riverpod VS MobX

From a library standpoint, I would recommend https://riverpod.dev over any other state management libraries for productivity purposes.

I have the following code. When I hot reload I get an error like this. Apparently this is fixed in dart 3 and Remi mentions a solve here. I am unclear how to refactor my code to achieve the solve without upgrading Flutter to an unstable version (which I've tried and cannot use because of certain render issues).

I saw this official example but it doesn't use riverpod_generator : https://github.com/rrousselGit/riverpod/blob/master/examples/todos/lib/todo.dart

Looking at the riverpod.dev docs, I saw that they were using Docusaurus which led me to creating this site. You can think of it as a guide or your go-to when trying to build gRPC servers and clients using Dart. It's open source hosted at this repo and everyone is really invited to Collaborate.

Riverpod Docs

I think you might need to use a state management if you want to keep the username and email always in scope in your application. Consider using riverpod or provider

You're right, it's Riverpod.

Sources: Riverpod: https://riverpod.dev REST: https://github.com/codeReview-youtube/flutter_auth_api PROJECT: https://github.com/codeReview-youtube/flutter_rest_riverpod_authentication

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

MobX

Mutable-based: leverages proxy to create mutable data sources which can be directly written to or reactively read from. Candidates in this group are MobX and Valtio.

Looks good! FWIW I always felt the observable pattern much more intuitive than the redux/reducer style. Something like https://mobx.js.org/

Things get hairy in both, but redux pattern feels so ridiculously ceremonially to effectively manage a huge global state object with a false sense of "purity".

Observables otoh say "fuck it, I'm mutating everything, do what you want with it".

MobX Documentation

There's also others libraries like https://github.com/mobxjs/mobx which aren't specific to RN but can be used in any JS environment.

Valtio is like simplified MobX

Link: https://mobx.js.org

But I want to impress upon you that this is just only one of many patterns you can use this hook for. While this is subjective, I am personally not a huge fan of Redux and this type of pattern. It has its merits, but I think once you want to start layering in new patterns for actions, Mobx, Zustand, or XState are preferable in my personal opinion.