This guide is editorial content prepared for this website. It is not presented as a published personal article by Nihat Akbuğa or an internal application document.
The boundary of change
Organizing a mobile project's folders by layer can improve readability. The more important question is which parts change together when a feature changes. Keeping camera data mappings and a device list screen in one large module can gradually make dependencies harder to see.
Feature-based organization brings together the parts of a user capability. Layer separation can still be maintained within that boundary.
features/
device_list/
data/
domain/
presentation/
camera_stream/
data/
domain/
presentation/
Does every class need an interface?
Abstractions should support boundaries that are expected to change and meet testing needs. Layers that merely forward a method to another class can make a project harder to understand. The scope of the domain layer depends on the complexity of its business rules.
Flutter's architectural recommendations emphasize separating the UI and data layers and defining clear responsibilities. They do not mean applying the same folder tree to every application.
The cost of shared code
Before moving a component into a shared area, consider whether it really represents a shared concept. Two visually similar screens can have different business rules. Sharing too early can couple features together.
A feature boundary should be considered alongside its public data contract, error behaviour, and lifecycle.
Testable behaviour
A repository boundary can make it easier to use different data sources in tests. The real value remains in testing observable user behaviour: loading completion, retrying after an error, and retaining existing data.
Source
Flutter — App architecture recommendations. The example folder tree is illustrative and does not represent the source structure of a private project.