Ghosts Of The Flutter Machine

Well, it’s now waiting for Material Design 3(Material You) to drop in the form of new Flutter SDK updates, and we now face again how the dynamics of Flutter Dev Process works as far as UI improvements; rather than how the Flutter SDK team intends it to work.

Is there a best practice way to solve this in using the Flutter Framework? Yes, which is exactly why I devote time to modify the Flutter Skeleton Template App to find all the best practices and include them.

So let’s see the flutter tricks to handle the fact that we will never see the perfect Flutter SDK where all the Flutter UI components are theme’d. And yes, other UI frameworks work the same damn way!

Where Do We Put The Business Logic Of The Platform Theme Differences

In targeting diverse platforms, we have two points of divergence. Apple uses a different native system and has 4 theme modes; And, Android only has two themes. So we have to abstract logic out so that we have a very thin layer of business logic in the UI method call.

Let me show you the start: