The Translation Problem Still Exists
Figma solved collaborative design years ago. Multiple cursors, real-time editing, version history—that battle's won. But there's still a gap that every product team feels: the moment a design leaves Figma and enters the world of code. That's where things get messy.
The good news? Figma's clearly aware of this. Dev Mode and Code Connect are solid steps toward keeping design and code in sync. Engineering managers report that before these features, maintaining design system documentation felt nearly impossible. Now, developers can inspect components and see actual code mappings right in Figma. That's meaningful progress.
But here's the thing: it only works in one direction. Designers push specifications forward, and developers implement them. When code changes, though, that information doesn't flow back. Teams are building custom plugins to bridge this gap—one engineering manager created a Variables Converter plugin specifically to translate Figma variables into CSS, React, Swift, and Compose. That's users solving their own problem, which means there's a real opportunity here.
Imagine if design tokens automatically generated code across platforms and stayed in sync as designs evolved. No manual translation, no drift between design system and implementation. Just a true single source of truth. That would complete the workflow Figma's already started building.
The Nested Interactivity Constraint
Here's a scenario every product designer has encountered: you're building a card component with a clickable area, but it also needs a favorite button in the corner. Or a table row that's selectable, with action buttons in each cell. Or a modal containing a form with interactive inputs. These aren't edge cases—they're fundamental UI patterns.
Figma currently blocks this. Interactive components can't be nested inside other interactive components. There's a debug toggle to suppress the warning, but that's users telling Figma they need to do this anyway. When people bypass safety rails to accomplish their design goals, it's worth asking whether those rails are protecting the right things.
The constraint makes sense from a technical perspective—nested event handlers can create ambiguous interaction states. But real-world interfaces require exactly this kind of complexity. Competitors handle it with explicit override controls that let designers specify interaction priority. Figma's component system is sophisticated enough to support this pattern, and teams would benefit from not having to flatten their component hierarchies or duplicate components to work around the limitation.
From Prototype to Production
The most interesting shift happening at Figma isn't in the design tools themselves—it's in what happens after design. Figma Make lets users build functional applications without writing code. People are creating farmer marketplaces, real estate sites with lead capture forms, and interactive dashboards. Product managers are using Make prototypes as alternatives to traditional PRDs, which is a fascinating workflow evolution.
But the journey stops at export. Users generate responsive, production-ready code and then hit the same deployment friction that no-code tools were supposed to eliminate. They're back to configuring hosting, setting up deployments, managing domains—all the technical barriers that prevented them from shipping quickly in the first place.
Figma Make already proves that non-technical users can create sophisticated applications. Adding one-click deployment to Vercel, Netlify, or AWS would complete that promise. The integration points exist, and Figma already embeds Make prototypes across its platform. Making deployment the final step would transform Figma from a prototyping tool into an actual product launch platform. For founders and PMs without engineering resources, that's the difference between validating an idea in days instead of months.
What This Means
Figma's expanding beyond being a design tool, and it's doing so thoughtfully. The pieces are in place—AI-powered code generation, component systems, collaborative workflows. The opportunity now is connecting those pieces into complete end-to-end flows. We used Mimir to pull this analysis together, and what stood out most wasn't any single feature, but rather how close Figma is to eliminating the traditional boundaries between design, development, and deployment. That's where the real value lives for product teams.