Octopus.do vs Lucide
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.
Lucide is in a steady icon-addition cadence — eight minor releases in six weeks, mostly community PRs.
Lucide is releasing roughly twice a week along the 1.x line, with each minor adding 1–6 community-contributed icons (blender, broccoli, sticky note variants, repeat-off, waves-vertical, folder-bookmark, astroid, heart-x, layers-minus, bell-check) and refining existing ones (text-cursor, landmark, candy-cane, volleyball). Framework adapters (Svelte, Vue, Angular, React) receive small fixes alongside. There is no structural work in this window — it is a contributor-flow optimization.
The project sits in healthy steady-state. Low-friction PR throughput, regular minor versions, and no large refactors suggest Lucide has settled into being the default fork-and-extend icon library for designers and the maintainers are protecting that contributor pipeline rather than pushing a roadmap. Framework adapter parity is being maintained in lockstep with the core icon set.
Expect another 1–2 icons (or refinement PRs) per minor over the next few weeks, plus a framework-adapter patch as upstream Svelte/Vite/Vue dependencies shift. No 2.0 cut is signaled in this window.
See more alternatives to Octopus.do →
See more alternatives to Lucide →