Thanks :-). Try it and let me think what you think about.

Provider and Maestro are different tools:

Provider is a great tool to share a value to all widgets of a subtree and make them aware of the changes of this value. But you'll need other objects (like ChangeNotifier for example) to use it as part of your app state management. Provider does not force you to use ChangeNotifier, Bloc, or whatever, it's agnostic to that.

The goal of Maestro in the other hand is to help you to manage your app state, and while you could use it to share values to all widgets in a subtree, it's less flexible than Provider. Its philosophy is to separate the data (which are a part of the app state) from the objects which manage that data. The data should be immutable, and you should provide a new instance when you want to change the data. Therefore Maestro is in my opinion less verbose than Provider when you want to use it for app state management.

There are no reason to use Maestro over Provider + X as your app state management apart your personal preferences. If you prefer to use immutable objects as storage for your app state and you don't want to care about the BuildContext when you want to read/write a value, then you can go for Maestro and Composer. If you prefer ChangeNotifier or Streams, Maestro is not built to handle this.

Disclaimer: Maestro is for the moment an experiment, if you want something fully tested and stable you may want to go with Provider + X. Otherwise try Maestro, and make your own opinion ;-)