Get your free personalized podcast brief

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

Stop trying to create pixel-perfect designs in Figma; its rendering of type and color will never match the browser. Instead, embrace Figma as a rapid, low-fidelity storyboarding tool. Sketch out interaction flows with simple shapes, then feed those images to an AI to build the real thing.

Related Insights

Vercel's Pranati Perry explains that tools like V0 occupy a new space between static design (Figma) and development. They enable designers and PMs to create interactive prototypes that better communicate intent, supplement PRDs, and explore dynamic states without requiring full engineering resources.

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).

Designing AI experiences in Figma is misleading because it only captures the ideal "golden path." Prototyping in code with live AI models is essential to understand and design for latency, errors, unexpected responses, and the true user "feel" of interacting with an unpredictable system.

To rapidly iterate on mobile UI, Lynn sketches screens on physical index cards, which have a similar aspect ratio to a phone. He then photographs these low-fidelity mockups and uses GPT-4's image generation to "upscale" them into high-fidelity designs, bridging the gap between physical brainstorming and digital prototyping tools like Figma.

When building his own site, MDS doesn't aim for pixel-perfect Figma files. He gets the design to 85% completion, establishing the core direction, and then moves to code to finalize details like hover states and animations where the interactive "feel" is paramount.

For a solo founder moving fast, a comprehensive Figma UI kit is often a waste of time. Instead, use Figma at two extremes: for very rough structural exploration (even wireframing with screenshots) and for creating specific graphic assets (gradients, icons). Build the details directly in code.

Before writing code, you can string together hyperlinked screenshots in a design tool like Figma. This creates a 'hacky' prototype that feels like a fully built app to potential customers, allowing for rapid, low-cost user testing and validation.

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.

Instead of starting in Figma, prototype complex web animations using "gray boxing," a technique from game development. By using basic shapes and code (like HTML/CSS/3JS) to define the core flow and feel, you can validate the interaction's energy before investing in detailed visuals.

Figma's success as a general-purpose design tool (useful for posters, floor plans, etc.) is precisely what makes it suboptimal for software development. Its WebGL-based canvas is fundamentally disconnected from the DOM, creating a "pretty picture" that requires a separate, costly engineering effort to translate into code.

Use Figma for Rough Interaction Storyboards, Not Pixel-Perfect "Lies" | RiffOn