The preview looks aligned while its interaction state has already drifted.
Fast regeneration protects momentum, while visible state mapping protects trust in the prototype.
Who you’d be doing this for
“I showed the flow in review, then the disabled button still submitted when someone clicked it.”
Ewa Ivanov · UI/UX Designer
She maintains a shared product flow in Figma and uses Figma Make to give product and engineering an interactive version to review.
What is at stake
Selected and disabled states look right in the generated prototype but behave like their earlier versions in the preview, so a review can approve an interaction that fails on the first click. You have to weigh a fast recovery against making the mapping clear enough for your team to trust.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fast regeneration vs trustworthy behavior
- shared component semantics vs local recovery
- visual fidelity vs interaction fidelity
- release stability vs immediate relief
Why Figma
Figma Make sits between shared design foundations and the prototypes product teams use to decide what gets built.
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.