LottieFiles vs Octopus.do
Side-by-side trajectory, velocity, and editorial themes.
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.
Octopus.do is becoming the planning stage that feeds Figma, AI site builders and docs.
Octopus.do is repositioning from a standalone visual sitemap tool into the front of a production pipeline. Recent releases rebuilt its core editor on a modern foundation (adding columns, tables and alignment), shipped a Figma plugin that turns an Octopus project into a high-fidelity, variable-driven prototype, and added export paths — Word, an Octopus XML import/export format, and an AI-prompt export for website generators. The common thread is moving structured plans out of Octopus into wherever the work continues.
The direction is to own the planning and content-structuring stage and then hand off cleanly to every downstream tool. The Figma prototype generation is the most ambitious of these bridges, collapsing the usual gap between sitemap and design. The AI-prompt export and XML format hedge across the other paths teams take — AI site builders and external tools — so Octopus stays upstream regardless of what users build with next.
Expect deeper AI-assisted handoff (richer Figma and prompt generation) and continued editor capability buildout now that the rewrite gives Octopus a faster foundation to ship on.
See more alternatives to LottieFiles →
See more alternatives to Octopus.do →