Choosing A Flutter State Management Solution

There is an easy way to choose a Flutter State Management Solution, let me show you how.

What Are We Building

What are we building? Unless you ask that question, you will get lost in all the Flutter State Management Solutions out there.

What Are We Building:

1. Does my app have deep widget trees, i.e. complex UI screens?

2. What does our OOP Architecture require in the form of communicating across application layers?

Let’s go through this step-by-step.

If your app has a simple thin widget tree UI screen, then you obviously could use Inherited Widget and Inherited Models. It’s the other thing that gets forgotten and where developers run into trouble.

OOP Architecture

The Dart is a mixed OOP and FP language. We still need to do an OOP architecture implementation, as FP is not mature enough to do all that OOP architecture can do just yet. Not to mention that FP math concepts are still a bit unreachable for most front-end developers.

The problem the architecture solves is how to get the Domain and the app API and 3rd party APIs to communicate with testing, the presentation layer, and the UI layer. The state solution…