Bolt turns Figma files into apps
Bolt.new at $40M ARR
Bolt is pushing design tools toward becoming software factories, not just mockup canvases. The important shift is not that a designer can generate code, but that a Figma file can become a working app inside the same flow where teams already choose layout, colors, and components. That removes a handoff step, lets PMs and designers test real behavior faster, and makes the prototype increasingly close to production software.
-
The old workflow was, design in Figma, hand specs to engineers, then rebuild in code. Bolt changes that by turning visual work into a starting codebase, similar to how v0 also uses Figma links to generate UI, which shows this is becoming a product category, not a one off feature.
-
This matters most for PMs, designers, and design engineers who want something real enough to click, share, and test. Internal research shows teams are already skipping static mockups and going straight into Bolt for proofs of concept that look and behave like actual products.
-
The boundary is blurring, but not disappearing. The winning tools still need a clean path from visual editing to code editing, because many projects start with prompts and layouts, then move into deeper engineering work in Cursor, local repos, or enterprise codebases before they are truly production ready.
The next phase is a stack where design systems, prompts, and production code live in one loop. As Figma adds prompt to app features and Bolt moves deeper into enterprise codebases and company design systems, the strongest products will be the ones that let teams move back and forth between canvas and code without rebuilding the same app twice.