Flutter project structure

[falconint]

How do you structure and organize your Flutter projects when contributing to open-source repositories? Do you follow a particular folder structure (like MVVM, Clean Architecture, or feature-based), or do you keep it simple until the project grows?

[rohanirshad]

I usually keep things simple in the beginning (basic folders like models, views, widgets, services).
As the project grows, I move to a feature-based structure where each feature has its own view, controller/viewmodel, and model.
For architecture, I prefer MVVM with GetX since it’s lightweight and clear, and most importantly, I ensure the structure is well-documented and consistent for contributors.

[falconint]

helo

…

On Sat, Aug 23, 2025 at 1:14 AM Muhammad Rohan ***@***.***> wrote: I usually keep things simple in the beginning (basic folders like models, views, widgets, services). As the project grows, I move to a feature-based structure where each feature has its own view, controller/viewmodel, and model. For architecture, I prefer MVVM with GetX since it’s lightweight and clear, and most importantly, I ensure the structure is well-documented and consistent for contributors. — Reply to this email directly, view it on GitHub <#1393 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BWMHE2OKDRA6NMIH36RV3BT3O52Z5AVCNFSM6AAAAACES4EX4KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMJZGMZDENI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Gupta-02]

“Honestly, when you start a Flutter project, everything just sits in lib/ and it feels fine at first. But the moment your app grows, it’s like dumping all your clothes in one drawer — messy and hard to find stuff.
A cleaner way I like is to break it down into:
core for common stuff like themes, colors, helpers.
features where each feature (like auth, profile, chat) is its own little folder. Inside it, I split into data (APIs, models), domain (the logic), and presentation (the UI).
services for shared things like Firebase or notifications.
widgets for reusable components, like buttons or loaders.
This way, if there’s a bug in login, I know it’s in features/auth, and if I add a new feature, I just drop in a new folder without touching the rest.
But yeah, if it’s just a small hobby app, I don’t over-engineer. Start simple, and only add structure when the app actually needs it.”