New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decide a State Management #2
Comments
I would disagree with using GetX Also GetX acts like a whole new framework upon flutter. I would suggest using BLoC or Provider/Riverpod as they are battle tested and does one thing right that is state management. |
Using very_good_cli is preferable. It use bloc state management. |
Please read the very_good_cli |
I'd suggest Riverpod |
Checked out this appwrite_flutter template https://github.com/lohanidamodar/flutter_appwrite_starter |
I'd suggest Riverpod too. |
Can someone take up this task to re-structure the code to add statement management using Riverpod? Also I need help with initializing appwrite in flutter? |
I honestly cannot contribute with code rn as I already have a lot on my plate. I can help with issues and PR reviews. We can do a project as features. Similar to what it gives with the skeleton example app |
Riverpod in my case |
I would have loved to use cubit but it seems Riverpod will have it, in that case, that's cool too. so yes Riverpod. |
PR #11 |
Decide a state management package, developers have their preferences. Needs to be decided before conrtibutions begin.
I'd suggest the GetX State Management since:
The text was updated successfully, but these errors were encountered: