mobx.dart VS drift

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

I don't have a preference for SQL vs NoSQL; the app data is simple enough (think something like a note-taking app that can sync if you have multiple devices) that I do not think it matters. However, it would be really nice if direct device-to-device sync is supported so I don't need to bother with accounts or cloud. Some of the options I've found: - Couchbase Lite for Dart - sync is an enterprise feature, but Couchbase Lite for Dart is a community-built solution. Not sure how well that will work. - firebase - doesn't seem offline-first, just allows for temporary loss of connectivity - realm with Device Sync - seems most promising - ObjectBox Sync - no user-specific data sync. All data is sent to all app users! - drift + roll my own sync: yikes!

I have been using drift (since back when it was still called moor) for a long time now and really like it. The developer is responsive and quickly updates his package when new Dart versions come out.

There are a few people using https://github.com/simolus3/drift/tree/develop/extras/drift_postgres

You could try https://github.com/simolus3/drift/ with https://litesync.io/en/ it would be uncharted territory but if it worked it would be really interesting. The forum, https://litesync.io/forum/?q=mobile says its available for React Native. So it would probably work just fine in Dart. It does not support ConflictResolution. It appears you can evaluate it for free and the license cost is fairly inexpensive.

For an expense tracking app, we need to store the user's expenses and categories. At least for the first version, we're just going to store the data locally on the user's device. For this, I went with Drift, which is built on top of sqflite. For less critical data such as the theme and user preferences, shared_preferences is used instead.

I'd personally take a look at Drift instead. I've used it on a few different commercial projects now and it's very well built, one of the gems of the Flutter community IMO: https://drift.simonbinder.eu/

I'd run with Moor/Drift all the way then. https://drift.simonbinder.eu/