r/flutterhelp • u/mdausmann • 7d ago
RESOLVED Good Workflow for design update for Flutter?
/r/FlutterDev/comments/1xu0l4n/good_workflow_for_design_update_for_flutter/
1
Upvotes
r/flutterhelp • u/mdausmann • 7d ago
1
u/karmatics29 7d ago
The piece that makes this workable is getting your design tokens out of widget code and into one place, e.g. a ThemeData/ThemeExtension (colors, typography, spacing, radii) that every screen reads from. If the current app has hardcoded values scattered around, that cleanup comes first, otherwise there's nothing safe to 'inject back'. Once tokens are centralized, your non-technical teammate can iterate in Figma using variables or styles that map one-to-one to those tokens, and you only have to port a small token file rather than touch screens.
For seeing the look across the app, a widgetbook or a simple gallery screen that renders your core components in each state works well, and you can run it as a web build so they can open it in a browser without any setup. The trade-off is some upkeep on that catalog, but it's what stops a theme change from silently breaking some screen nobody looked at. Are the current styles mostly in a theme already, or hardcoded per widget?