Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Starting digital transformations solely within text-constrained code environments limits early creative visual craft. Explorative visual work benefits from unrestricted visual tools like Figma or paper sketches, whereas product experience and interactive coherence are best built directly in living codebases.

Related Insights

Contrary to traditional digital design, the modern AI-assisted workflow involves broad, conceptual exploration on canvas-like tools (e.g., Paper) and sweating the final visual details directly in code. Pixel-nudging in design software like Figma is becoming obsolete for last-mile fit and finish.

The debate over designing in code versus a visual canvas is outdated. The modern workflow isn't about choosing one, but fluidly moving between both tools based on the task: canvas for broad exploration and code for deep, interactive prototyping.

AI-powered "vibe coding" is reversing the design workflow. Instead of starting in Figma, designers now build functional prototypes directly with code-generating tools. Figma has shifted from being the first step (exploration) to the last step (fine-tuning the final 20% of pixel-perfect details).

Rather than treating Figma as the sole source of design truth, modern makers can generate UI entirely in code and sync components back into Figma via automated plugins. This keeps the codebase canonical while still leveraging canvas tools for rapid macro visual evaluations and spacing nudges.

Historically, design workflows moved from low-to-high fidelity due to tool constraints. AI tools like Codex remove these barriers, allowing designers to begin with functional wireframes in code for immediate interaction testing, bypassing static sketches.

As designers code more, the definitive version of the product lives in production, not Figma. This leads to messier, more ephemeral design files, often composed of screenshots with new elements overlaid, a major shift from maintaining pixel-perfect Figma libraries.

Instead of creating static mockups in Figma, Cursor's design team prototypes directly in their AI code editor. This allows them to interact with the "life states of the app" and get a more realistic feel for the product, bridging the gap between design and engineering.

John Bai from Cursor still begins in Figma to quickly visualize concepts and gain conviction. Figma acts as a storyboard and idea repository before he uses AI tools to translate those ideas into high-fidelity, interactive prototypes.

Dylan Field envisions a future where design tools are so integrated into development that designers can issue pull requests directly to production from a visual canvas. This blurs the line between design artifacts and production code, making design the primary language of creation.

Figma's CEO argues that while agentic coding systems are powerful, they risk being too linear. True product innovation requires exploring a wide option space through design, using systems and components to ensure a cohesive user journey. Relying solely on code generation can lead to a suboptimal product, even if it's built quickly.

Figma Excels at Explorative Visual Craft While Code Best Serves Functional Products | RiffOn