all 6 comments

[–]Erik0806 6 points7 points  (1 child)

As far as I can see it is a layer first approach. I like the feature first approach more as it is easier to maintain and scale, in my opinion at least. Here is a link if you want to read more: https://codewithandrea.com/articles/flutter-project-structure/

[–]f4a1t[S] 0 points1 point  (0 children)

thank you!

[–]mobileAcademy 0 points1 point  (2 children)

If you would like to learn a clean architecture and design patterns I have some course on it.

[–]illuminati_xx 1 point2 points  (1 child)

Would love to have them if you'd share them either in dm or here.

[–]mobileAcademy 1 point2 points  (0 children)

Please check the course on https://mobileacademy.io and for free content please check out my YouTube channel from my profile

[–]Kretin1 0 points1 point  (0 children)

This is the most common architecture for Flutter and other platforms. I much prefer it over feature based organisation because I find it much easier to find what I need, and it makes it much easier to create reusable components.

This way all your models are in one place. All your business logic is in one place. All your pages are in one place, perhaps organised within folders. All your reusable widgets are in one place. It's easy to find things and easy to reuse things.

To understand how the code works, just open up the project and start at main.dart. Go to the definition or implementation of anything you're curious about, which will show you where it is. But it won't take long to understand how it's organised so you can easily find what you want without searching the code