Octopus.do vs LottieFiles
Side-by-side trajectory, velocity, and editorial themes.
Octopus.do is doubling down on its handoff layer — IA in, prototype/doc/AI-prompt out.
Octopus.do is positioning itself as the upstream planning tool that feeds anywhere downstream. Recent shipping centers on export and interop: a Figma plugin that generates a hi-fi prototype from an Octopus project, .docx export, AI-prompt export for website-generator handoff, and an Octopus XML format for round-trip project import. A January pricing change ending grandfathered Pro plans formalized the company's commitment to keeping that investment going.
The strategic bet is that website builders, designers, and content teams should plan structure in Octopus and then ship to whatever production tool they use — Figma, Word, an AI website generator, or another Octopus instance. Each release in the past quarter is a new handoff lane. The shape of this is less a product expanding feature surface and more a hub deliberately growing its spokes.
Watch for the next spoke to target code-generating tools or popular website builders directly — Webflow, Framer, or Wix exports. The AI-prompt export experiment is the early read of that direction.
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 Octopus.do →
See more alternatives to LottieFiles →