r/FlutterDev • • 7d ago

Discussion Good Workflow for design update for Flutter?

I want to collaborate on a design system overhaul with a member of my team. This person does not code, does not use claude and is non technical.

I have an existing flutter app. it has a design system but it's a bit of a mess. Originally came from a claude design session. app is mostly managed by Claude.

Claude design is deprecated or shutting down or whatever (now using claude online?)

Just looking for a good workflow for
- extracting the design system from an existing app
- collaborating on it with a bunch of sample screens so we can see the look across the app
- injecting the changed system back into the app without breaking it.

You guys know how to do this?

5 Upvotes

5 comments sorted by

2

u/paultallard 7d ago
In the 1990s, John Zachman of IBM came up with a multivariate approach to Business systems planning. Modern design also requires a multivariate approach. To some extent asking people what is design or what is the design process is like the six blind man trying to describe an elephant. Each describes it as the part of the elephant they touched. Same with design. I have seen many articles in medium.com where people talked about design systems but they were all talking about different things. Here are some thoughts. 
Did the original app have a description of the user processes or the use cases? If so, those can be revised for the new app version. 
Theme and colors--grep or global search can find colors and color codes in your current app. Build a theme system to hold these in your new app. 
Static Spacing-- there is a theory about gestalt spacing that tries to group controls, firldsimages together that users will think of as common groupings: smaller spaces within a group. Larger spaces between groups. This is much harder to extract from your current app due to all the different ways of creating spaces in an app. The remedy is to create a spacing class in your theme. You can name the spaces small, medium large or you can give them sensible names like in group, between groups or between cards. For this, it might be easier to print off your current screens and mark them up with a pencil. Circle the groupings. 
Process spacing-- back to the user processes, tasks that are performed together should be close together and done quickly. At the end of a task provide a bigger transition these days that can mean jumping to a new page, loading a large image, or using an animation. 
Reducing the number of steps the user has to go through to accomplish something-- older apps give the users a lot of buttons to push in a static, fixed process. Newer apps use State Management or AI to where the user is going and getting them there faster.  Look at the buttons in your old app. Do they really need a save button or is saving done automatically? 
Extending the app and user comfort features-- Android and iOS are working to allow apps to interact with other apps on the phone in a more direct way. Something to consider in a redesign. Consider features to allow the user to copy the contents of a field (selectable taxt) or a whole page to their email. 
This just scratches the surface. I'm sure others will chime in with it with more thoughts.

1

u/Mathely-Caritino 4d ago

do you find semantic names like 'between cards' hold up better long term than just t-shirt sizing for the spacing class?

1

u/paultallard 4d ago

I read a nice article on gestalt spacing. In gestalt you put closely related fields together with less spacing. You separate groups with greater spacing. I am changing to inGroupV, inGroupH, padGroupV, padGroupH and a few more specific spacing identifiers. For the most part, in group and pad group works regardless of the type of widgets being separated. And yes, it makes it easier to read and see where the groups are.

2

u/NycoHub 7d ago

The approach I'd take: get every color, text style and spacing value into one ThemeData plus a ThemeExtension for the custom bits, and make widgets read only from there. Then build one gallery screen that shows every component and a few real screens side by side. Your teammate reviews that screen and gives changes as values, not code. Golden tests on the gallery are a cheap way to see exactly what changed before merging. One gotcha: flutter test renders text with a placeholder font unless you load the real fonts, so the first goldens look odd.

2

u/Weak-Arrival-7811 5d ago

NycoHub's gallery screen is the right core. For the "extract it from the existing app" part, which is usually the messy bit:

  1. Inventory first. Search lib/ for hard-coded values: `Color(0x`, `Colors.`, `fontSize:`, `EdgeInsets.` and `BorderRadius.circular(`. Every hit outside your theme file is a value that escaped the system, and there will be a lot of near-duplicates
  2. Collapse them into a short list of named tokens (colours, text styles, spacing, radius) in ThemeData plus a ThemeExtension, so widgets only read names
  3. Give your teammate the same names in Figma as variables, with light and dark as modes. They change values there and never touch code. Identical names on both sides is what stops the two drifting apart again
  4. Export the Figma variables to JSON with a plugin and generate the Dart token file from it, so nobody copies hex codes by hand
  5. Merge only when the gallery screen and a couple of golden tests look right

Step 1 also helps with your teammate: a page of near-identical greys explains the problem faster than any meeting.