I know there are some flutter architecture pattern like MVC, MVVM. Also there are some flutter state management approaches like setState, Provider, Getx, Mobx, BloC/rx and inheritedWidget etc.

As I understood state management approaches are used to manage the state of the app and as I understood flutter architecture patterns are used as architecture of the flutter app(I m bit doubt about my flutter architecture patterns definition.)

So I just need to know is there any relationship between flutter state management approaches and flutter architecture patterns. or do we need to use flutter architectural pattern to organize our state management code.

CodePudding user response：

Short answer: No. They are different. You can use any architecture with any state management solution. For example most of the state objects resides inside the controllers of MVC (where controller holds logic). But in DDD, it's on the presentation layer.

In summary, state management solutions used to provide the states to the screen, where patterns/architecture used to organize the whole codebase.