Scalable App Architecture – CodeWithAndrea
This scalable app architecture design is inspired by Andrea Bizzotto. Full documentation of this design can be found here. In addition to that, you can use a VSCode extension called Flutter Feature Scaffolding for easily generating the features’ folders. This design is using BLoC state-management solution, and for more information on BLoC library, I would strongly suggest you to follow their official documentation.
This project contains everything that you will need in order to immediately start developing your highly scaled application. You can also call this folder structure as Feature-first (layers inside features) design.
About the folder structure
lib/
├── src/
│ ├── common_widgets/
│ │ └── common_button.dart
│ ├── constants/
│ │ └── colors.dart
│ ├── exceptions/
│ │ └── routing_exception.dart
│ ├── features/
│ │ ├── address/
│ │ │ ├── data/
│ │ │ │ ├── datasources/
│ │ │ │ │ └── address_datasources.dart
│ │ │ │ ├── models/
│ │ │ │ │ └── address_model.dart
│ │ │ │ └── repositories/
│ │ │ │ └── address_repositories.dart
│ │ │ ├── domain/
│ │ │ │ ├── entities/
│ │ │ │ │ └── address_entities.dart
│ │ │ │ ├── repositories/
│ │ │ │ │ └── address_repositories.dart
│ │ │ │ └── usecases/
│ │ │ │ └── address_usecases.dart
│ │ │ └── presentation/
│ │ │ ├── bloc/
│ │ │ │ ├── address_bloc.dart
│ │ │ │ ├── address_event.dart
│ │ │ │ └── address_state.dart
│ │ │ ├── pages/
│ │ │ │ └── address_page.dart
│ │ │ └── widgets/
│ │ │ └── address_widgets.dart
│ │ ├── authentication/
│ │ │ └── (...)
│ │ ├── cart/
│ │ │ └── (...)
│ │ ├── checkout/
│ │ │ └── (...)
│ │ ├── orders/
│ │ │ └── (...)
│ │ └── products/
│ │ └── (...)
│ ├── localization/
│ │ ├── app_bn.arb
│ │ ├── app_en.arb
│ │ └── localization.dart
│ ├── routing/
│ │ └── routing.dart
│ └── utils/
│ └── utils.dart
└── main.dart
You might notice that some files are just dummy (like api.dart, model.dart).
They are placed there just for git to take the folder structure into consideration.
Leaving those folders empty won’t let git to take them into consideration. Since this is mostly a startup project, I was thinking of offering you the standard folder structure from the start. Of course, this may change multiple times, improving every time more and more.
Why this design pattern?
This architecture is made of four distinct layers, each containing the components that our app needs:
➮ presentation: widgets, states, and controllers
➮ application: services
➮ domain: models
➮ data: repositories, data sources,
and DTOs (data transfer objects)
Of course, if we’re building just a single-page app, we can put all files in one folder and call it a day. 😎
But as soon as we start adding more pages and have various data models to deal with, how can we organize all our files in a consistent way?
In practice, a feature-first or layer-first approach is often used.
Layer-first: Drawbacks
This approach is easy to use in practice, but doesn’t scale very well as the app grows.
For any given feature, files that belong to different layers are far away from each other. And this makes it harder to work on individual features because we have to keep jumping to different parts of the project.
And if we decide that we want to delete a feature, it’s far too easy to forget certain files, because they are all organized by layer.
For these reasons, the feature-first approach is often a better choice when building medium/large apps.
What about shared code?
Of course, when building real apps you’ll find that your code doesn’t always fit neatly into specific folders as you intended.
What if two or more separate features need to share some widgets or model classes?
In these cases, it’s easy to end up with folders called shared or common, or utils.
But how should these folders themselves be organized? And how do you prevent them from becoming a dumping ground for all sorts of files?
If your app has 20 features and has some code that needs to be shared by only two of them, should it really belong to a top-level shared folder?
What if it’s shared among 5 features? Or 10?
In this scenario, there is no right or wrong answer, and you have to use your best judgement on a case-by-case basis.
What is a feature?
Feature-first is not about the UI!
Feature is not about what the user sees, but what the user does:
➮ authenticate
➮ manage the shopping cart
➮ checkout
➮ view all past orders
➮ leave a review
In other words, a feature is a functional requirement that helps the user complete a given task.
And using some hints from domain-driven design, I decided to organize the project structure around the domain layer.
Once I figured that out, everything fell into place. And I ended up with seven functional areas that you can see on the right.
Note that with this approach is still possible for code inside a given feature to depend on code from a different feature. For example:
➮ the product page shows a list of reviews
➮ the orders page shows some product information
➮ the checkout flow requires the user to authenticate first
But we end up with far fewer files that are shared across all features, and the entire structure is much more balanced.
How to do feature-first, the right way?
In summary, the feature-first approach lets us structure our project around the functional requirements of our app.
So here’s how to use this correctly in your own apps:
☞ start from the domain layer and identify the model classes and business logic for manipulating them
☞ create a folder for each model (or group of models) that belong together
☞ within that folder, create the presentation, application, domain, data sub-folders as needed
☞ inside each sub-folder, add all the files you need
