If you’re building with Flutter and you’re wondering whether the Dart backend actually makes sense now, and what your real options are, I broke it down in a practical guide.
I write all my articles by hand for the first draft and the final polish. I do use LLMs in between to try to get a clearer message (to what I find appropriate).
I understand if you don't want to read it, but there is nothing dishonest about this article. I've lived through what I wrote with those 3 apps. Take it as you wish and have a good day.
My 2 cents: if you are big enough and the competition isn't as strong, users will give you a pass on some performance issues as long as they get the content they want.
I remember one time there was a random Philips TV that just kept crashing when the user tried to do "right" on the last item in a horizontal menu. The client kept testing on this TV, and we spent 3 weeks because my team lead at the time wouldn't trust me that I needed the TV to solve it.
They finally agreed to send us the TV. Solved the issue in 10mins.
I've noticed this as well. My best guess is either low hardware or just a bad solution.
If they planned to use a unified codebase for Prime app, they likely went with something HTML/CSS-based, which would explain the performance issues. I could be wrong, but it's just a hunch I have.
Any state management approach requires you to adapt your way of thinking, whether that be BLoC, Riverpod, Redux or anything you want to use.
Rivepod gained popularity because it's really simple to pick up: create a Notifier, create a Provider for it, and observe, while some other approaches require additional boilerplate, setup, and understanding.
Your approach would work if you are only observing that state from a single widget, which might not always be the case. Additionally, assuming useState is using setState under the hood means it will rebuild the whole widget on change, while with Riverpod, you have the flexibility to wrap any part of a complex widget into a Consumer or listen to only part of the exposed state on the Notifier with .select().
To put it simply:
- Notifiers are used for app state
- Hooks are used for ephemeral state (local widget state)
SEEKING WORK | CET | Remote Senior Mobile (Android/iOS/Flutter) engineer looking for work. Creating high quality mobile & TV apps is my passion.
Mobile architecture, clean code, SOLID principles, Unit and UI tests, CI/CD.
Skilled with Android, Flutter, Dart, Firebase, MongoDB, MVVM, Kotlin, XML & Jetpack Compose, Swift, SwiftUI.
Experience in agile environments, leading smaller teams, code reviews, pair programming, and mentoring.