mobx.dart VS provider

I'll also add that the MobX documentation is a great resource and much better than explaining than I am. If you want to explore a little more I definitely recommend checking it out.

The native way of state management in Jetpack Compose is `mutableStateOf` and `derivedStateOf`. It is an analogue of mobx.dart. Are you familiar with these concepts? What issues did you face with?

· MobX– It’s a popular technique since a long time and uses Observables, Actions and Reactions to notify the widgets of changes. It as initially designed to be used with JavaScript projects and then migrated to Dart to be used used with Flutter projects. It’s an annotation based package which generates the code using a separate package. Read more about it here.

For more examples and guides you can see the original documentation.

Having said that when it came to testing I did not find a good way to write the kind of tests I wanted, although the documentation for mobx in in Flutter is great https://mobx.netlify.app/ I found it lacking when trying to figure out how write robust unit tests. Luckily I found quite a nice approach that I'd like to share in this post.

MobX ⇨ State Management

Active development: low Github link

To make things a bit easier to use and more reusable, we are going to use provider library instead of InheritedWidget, including simplified resource management, reduced boilerplate, lazy loading and a nice listening mechanism to go with ChangeNotifier

Provider ⇨ State Management