don't get discourage about flutter recommendations, I give them a thumbs up for presenting a suggestion even though there is no right for all architecture and it can be a controversial topic. thanks that flutter gives the freedom to choose and create the architecture that fits your app needs.
They have "one to many" approach for Repository and ViewModel. But "one to one" to View? It's contraintuitive. For me it's one ViewModel to many Views.
don't get discourage about flutter recommendations, I give them a thumbs up for presenting a suggestion even though there is no right for all architecture and it can be a controversial topic. thanks that flutter gives the freedom to choose and create the architecture that fits your app needs.
Yes!! Big Archictecture coming through! Very well done!
bloc arch is the best
How would you use theme as a appwide state?
What about Command? It helps manage different states and triggers
Like in the days back when, missed your voice :)
Haha appreciate it ❤️
Riverpod architecture 👍
Hungrimind MVVM > Flutter MVVM - bought the Best Flutter Course
Wooo, thank you!
They have "one to many" approach for Repository and ViewModel. But "one to one" to View? It's contraintuitive. For me it's one ViewModel to many Views.
Yes that would work. Our approach is to name it differently if it can be used in many views.