Mobile component decisions are getting lost between the canvas and generated starter code.
Fast exploration protects iteration speed, while shared component conventions protect implementation consistency.
Who you’d be doing this for
“I watched three teams redraw the same mobile pattern this week because nobody trusted the generated version.”
Graham Evans · Mobile Design Systems Lead
Owns the shared component guidance that product designers and mobile engineers rely on across product areas.
What is at stake
Mobile teams are rebuilding approved interface patterns because generated output does not carry their mobile conventions. You have to weigh a fast pilot against the boundary engineers need before generated code reaches a pull request.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fast exploration vs. reviewable implementation
- mobile conventions vs. reusable patterns
- minimum access vs. meaningful validation
- design-system authority vs. engineering workflow ownership
Why Figma
Figma Make, Make Local, and Code Connect place the design-system boundary directly inside enterprise design-to-code workflows.
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.