Visily vs Lucide
Side-by-side trajectory, velocity, and editorial themes.
Visily crosses from AI mockups into shipping code, with code generation now built in.
Visily is an AI-powered UI design tool that publishes batched monthly updates. The recent arc has been about closing the gap between design output and a working product: Design Instructions and Deep Design mode in January raised the floor on AI-generated UIs, Figma import in February anchored the tool inside existing design workflows, and the March release adds outright code generation for finished designs along with a Plan Mode for ideation.
Visily appears to be narrowing toward 'design plus handoff' as the core promise rather than 'design with AI.' The Figma import + code generation pairing makes it a viable on-ramp for teams whose source of truth lives in Figma but who want a faster path to working frontend code. Plan Mode signals an upstream ambition too — rather than only generating final designs, the tool now wants to participate in the early ideation step where requirements get shaped.
Expect the code-generation surface to grow framework-specific (React/Tailwind first, more later) and tighter Figma round-tripping so designers can iterate in Figma and pull updates back through Visily for code regeneration.
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 Visily →
See more alternatives to Lucide →