Flux App Arch And State Management In Flutter Apps

I am going to show you how to implement Flux app arch and state management in flutter apps. But, first, I have to describe why we do not have MVC derived patterns anymore in both app arch and state management.

Why MVC Derived Arch App Patterns Became Irrelevant

So everyone is familiar with this:

Well, ahem, no you are not as you still see it without seeing it! The problem with all MVC derived patterns is that the model was directly coupled to the view. And, that started out in imperative programming as we had a one-time build of the app screen in most native frameworks. State, instead, was handled by lifecycle hooks in the Super-Controller-In-framework and small-c-controller pairing of the app arch itself.

So, in the imperative world, it was devised to use service locator IoCs to break that direct coupling between the view and the model. But, because the app arch was still tied to the framework building the whole screen one-time and then making state changes via the framework lifecycle hooks we still managed to call the assembled MVC derived patterns still MVC focused patterns.