Prototype behavior is visible in the canvas while its implementation intent disappears in handoff.
Designers need room to explore, while developers need a reliable signal about what must survive into production code.
Who you’d be doing this for
“Engineering asked whether the loading state was intentional, and we’d already shipped around it twice.”
Dokyun Tanaka · Design Systems Lead
Owns the component library used by product designers and developers across an enterprise product team.
What is at stake
Pilot teams are losing interaction intent after prototypes enter fast code-generation workflows. You have to weigh a clear developer signal against keeping exploration lightweight for designers.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- designer exploration vs developer certainty
- canvas simplicity vs durable implementation context
- shared system guidance vs local product intent
- faster code generation vs reviewed interaction decisions
Why Figma
Figma files sit at the point where shared components, prototypes, and production code meet for product teams.
Written with these in mind
Not your kind of problem? 45 more at Figma, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.