Replies: 1 comment
-
I don't think adding more layers on Stacked would benefit the codebase much. It's quite a bit of boilerplate and my goal is to create the simplest form of a scalable and maintainable code base. CLEAN architecture is on the other side of our direction at the moment. but I'm sure it can be done. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There are some articles (e.g. https://devmuaz.medium.com/flutter-clean-architecture-series-part-1-d2d4c2e75c47) discussing Uncle Bob's Clean Architecture in Flutter. This is a pretty clean way to decouple parts of the application, make it more testable, as well as restrict access to only the dependencies needed.
I think many consumers of stacked aim to build some sort of production ready application, which most times should keep clean scalability in mind. I personally am not experience with Clean Architecture, that's why I struggle how to structure this pattern for MVVM of Stacked in reference to StackedServices and ReactiveViewModels opposed to Blocs that are most commonly used in those Articles with Use Case classes.
I would love to see any type of ideas or example projects, that someone with more experience regarding Clean Architecture has 👍🏽
Here a sample folder structure for CA:
Here a sample flow for CA:
Beta Was this translation helpful? Give feedback.
All reactions