Asking The Wrong Flutter State Question

Google is wrong about State Solutions in Flutter. This is an opinionated way to choose a state solution based on app performance.

This is not to put words in the mouths of the Flutter Stakeholders at Google or any of the independent contributors to Flutter and Dart. But, based on computability, there are specific things you should not choose as an accessory to your state solution approach for your flutter app.

Background

ince we do not use ChangeNotifier for complex models in complex apps and, it’s a listener based Notifier; what would implementation would it be? Is it a Map or a List?

Yes, it’s a list based implementation. Now, do not get hung up on the have to avoid the

o(N^2)

problem as that is not what I am focusing on as far as performance. I am focused on the memory footprint.

Maps always are memory footprint smaller than lists.

Now for my own twist on the insight.

Flutter State Insight

Let me show you something: