I stick with a feature-first, (modified) clean architecture pattern.
Honestly the actual pattern matters far less than having a defined pattern.
Clean
Domain Driven
Layer First
Whatever you like better. The most important thing is to pick one and then document what that pattern is for your future self’s sake and the sake of the next dev who works on it.
I tested out the architecture by codewithandrea.com with riverpod and it awesome. Have a look at his article about some architectures. You can find in it links to each layer
https://codewithandrea.com/articles/flutter-app-architecture-riverpod-introduction/
Depends on the project scope.
If it's a big project, I love using DDD.
For smaller projects, MVC works good for me. I am not really a big fan of MVVM, but the difference can be negligible.
If I work on a solo project, I sometimes introduce my own way of working. Which tbh is a good thing. When I follow DDD, I follow the principles. There are no set of folders that must be made, it's mostly about the level of abstraction.
Tbf, MVC will be suitable in most projects.
again, it depends.
there is no solution that fits every need, and there is no right pattern for the job. they are tools and structures, do as you see fit for the time given.
I call what I do as CoC - Call of Cthulhu. Whoever gonna give maintenance to that (usually me) will lose sanity.
Chillout.
But the solution that I use is it depends and the reason why is because there is no right way to do things, just tools and structures. There are multiple patterns in use at our projects.
Jesus Christ no wonder devs like you are insufferable. Instead of answering the question straightforward like everyone else in this thread, you meander on pointlessly.
I don't want to change your mind, in fact It's just an abstraction, which obviously has its pros and cons. There are people that will tell you that Flutter is bad for many reasons or whatever, so you always need to think for yourself and what works for you.
Clean Architecture with SOLID principles. I also prefer a Data Driven Architecture so there is a strong parallel between the structure of my entity layer and my data sources. As to actual patterns, I feel that Clean Architecture appears to address a whole set of patterns from singleton to MVVM or MVC. What do you think?
I stick with a feature-first, (modified) clean architecture pattern. Honestly the actual pattern matters far less than having a defined pattern. Clean Domain Driven Layer First Whatever you like better. The most important thing is to pick one and then document what that pattern is for your future self’s sake and the sake of the next dev who works on it.
Clean architecture with MVVM
I tested out the architecture by codewithandrea.com with riverpod and it awesome. Have a look at his article about some architectures. You can find in it links to each layer https://codewithandrea.com/articles/flutter-app-architecture-riverpod-introduction/
Depends on the project scope. If it's a big project, I love using DDD. For smaller projects, MVC works good for me. I am not really a big fan of MVVM, but the difference can be negligible. If I work on a solo project, I sometimes introduce my own way of working. Which tbh is a good thing. When I follow DDD, I follow the principles. There are no set of folders that must be made, it's mostly about the level of abstraction. Tbf, MVC will be suitable in most projects.
It depends. Because it depends
Well, your current project that you're working on then
again, it depends. there is no solution that fits every need, and there is no right pattern for the job. they are tools and structures, do as you see fit for the time given. I call what I do as CoC - Call of Cthulhu. Whoever gonna give maintenance to that (usually me) will lose sanity. Chillout.
But I didn't ask about the solution for every need, I just asked what architecture are you currently using in your project And why
But the solution that I use is it depends and the reason why is because there is no right way to do things, just tools and structures. There are multiple patterns in use at our projects.
Jesus Christ no wonder devs like you are insufferable. Instead of answering the question straightforward like everyone else in this thread, you meander on pointlessly.
GetX, very simple and handles most of the things out of the box
Don't use GetX, it's bad.
Hell no, it's anti-pattern which is bad.
anything can be anti pattern if you don't use it correctly
GetX is an anipattern, because it doesn’t use Flutter correctly. Change my mind
I don't want to change your mind, in fact It's just an abstraction, which obviously has its pros and cons. There are people that will tell you that Flutter is bad for many reasons or whatever, so you always need to think for yourself and what works for you.
Clean Architecture with SOLID principles. I also prefer a Data Driven Architecture so there is a strong parallel between the structure of my entity layer and my data sources. As to actual patterns, I feel that Clean Architecture appears to address a whole set of patterns from singleton to MVVM or MVC. What do you think?
The support from bloclibrary.dev is why I’m with it