Lucide vs LottieFiles
Side-by-side trajectory, velocity, and editorial themes.
Lucide ships icons at a steady clip and retires its deprecated framework packages.
Lucide continues its steady cadence as a community-driven icon library: most releases add or refine individual icons, with periodic framework-package and tooling maintenance. The notable recent move is 1.17.0 removing the deprecated lucide-vue-next, lucide-svelte, and lucide-angular packages, completing the migration to scoped @lucide/* packages. Releases also fold in routine dependency bumps, docs, and build-tooling work.
The library is in mature, incremental mode - expanding icon coverage and tidying its distribution rather than changing direction. The deprecated-package removal and the new meta-json use-case requirement point to tightening contribution standards and a cleaner package surface. Cadence is high and contributor-driven.
Expect the steady stream of icon additions and refinements to continue, with consumers of the old framework packages needing to migrate to the scoped @lucide/* equivalents.
LottieFiles ships an MCP server alongside generative tooling — Lottie Creator is becoming AI-native.
LottieFiles is shipping aggressively across three threads: AI authoring (Prompt to Vector 2.0, AI-driven scene generation), agentic integration (Lottie Creator now connects to Claude, Cursor, and any MCP client), and creator-tool depth (curved-path animation, freehand vector drawing, version history, intelligent keyframe simplification). The .lottie file format gained multi-animation support, and a Figma plugin now translates Figma prototype interactions into production animations.
LottieFiles is positioning Creator as the canvas where motion design and AI tooling meet — both as a generation source (text-to-vector, scene generation) and as a target other AI assistants can manipulate via MCP. The Figma interaction-to-animation feature suggests a deliberate strategy of importing intent from upstream design tools rather than asking designers to redesign in Lottie Creator. File format work (multi-animation .lottie, smaller files at same fidelity) keeps Lottie viable as the underlying motion-graphics format on the web.
Expect deeper MCP-driven workflows — agents that take a brief and produce a finished Lottie file inside Creator without human authoring — and additional importers from After Effects, Rive, or Spline. The Figma interaction bridge is likely to be replicated for other prototyping tools (Framer, ProtoPie). Generative motion is a strong candidate for next major surface.
See more alternatives to Lucide →
See more alternatives to LottieFiles →