You Need THIS for Big Flutter Projects | Flutter Project Structure

Flutter Project structure must be properly chosen for Big Projects to Scale and Maintain your flutter project easily.
We will take a look how to structure the files in a flutter project and which flutter project structure should be used for small and big projects.
#flutter #project #structure

[nicoloagnoletti]

Very well done video!
I still want to suggest to make use of modularization (Flutter/Dart packages):
having a large project means you have to work with others, and restricting access only to the things that the single layer should access is a good way to make everyone respect the rules and work in the same way.
That plus the same you suggested (app/core, feature-first) is my way of choice

[RamyWahid]

This is really great video, Thank You so much

[gerardomiranda]

I like the app/core idea. But I would recommend against the feature first pattern for big projects. Reasoning is simple, you want the layers to be loosely coupled, so if the day comes when I need to, for example, use a different backend for a different client, it is easier to have a folder for each integration rather than have them all over the place

[rahuldange]

Good one!
My only concern is more about shared thing like what about controllers which can be used same for 2 packages or model class which can be used in multiple places?
Do I have to put them in shared too? then feature based architecture will wont be feature based for such multiple cases right?

[malcomgreen]

It will be great if you can explain what goes in service folder and domains and models

[abdallagaafar]

I really want to know the theme that you were using in VS code while recording this video?

Thanks for the amazing video btw !!

[ma_am]

What's the difference between MVC and MVVC and what you said?

[ftomnuc]

i understood both the approaches and i follow layered architecture every where so anyone can help me how feature first can be beneficial
@Lambda Dev

[aizuddineismail]

I love your idea. I was doing almost the same approach.
What caught my attention is cloud_functions folder. I just started working with firebase,
I was wondering why do you need cloud_functions folder in flutter app? Or maybe what does this folder contain?

Thank you for sharing your opinion on Project Structure !!

[cper_]

Hey bro, i just created first project in flutter, the size of project folder is 550mb and the apk in my mobile has 129mb why is it so large even for a simple project.
Please reply

[JEsterCW]

I know its 1 year old video, but its really bad video about architecture including the fact that you made the feature architecture incorrectly/poorly, each feature should have on shit inside the feature including models, widgets and all, when theres a need of sharable data or whatever you make a group for the feature or possibly think if theres any need of sharing something, if so then you make a grouped feature and make inside it a shared folder and those 2 features are being there by that youre limiting the range of scope in the tree to one position when you need put something outside in per feature architecture youre making common/shared folder outside the features and you put everything there including base widgets etc that youre building your more complicated widgets in the feature sub folders or you can make packages as you said in the end that also works if implemented correctly and its more maintable. This architecture is great for mid sizes apps if you can limit the ranges of usage of something in the codebase it can scale really well, but you showed really wack implementation of the per feature architecture. The per type is good for small apps, but it scales really badly.... theres many more architectures like domain driven altho i have to admit that you gave a good tip of making packages this is really great pattern, but rest i would throw to a trash honestly, lmao