Feature-Based Folder Structure for Flutter Projects

Why Feature-Based?

Traditional Flutter projects organize code by type: all widgets in one folder, all models in another, all services in a third. This works for small apps but becomes a nightmare at scale.

Feature-based structure groups all code for a feature together:

lib/
├── features/
│   ├── auth/
│   │   ├── domain/
│   │   ├── data/
│   │   ├── application/
│   │   └── presentation/
│   ├── transactions/
│   │   ├── domain/
│   │   ├── data/
│   │   └── presentation/
│   └── settings/
│       ├── domain/
│       ├── data/
│       └── presentation/
├── core/
│   ├── shared/
│   ├── theme/
│   └── navigation/
└── main.dart

Benefits

1. Discoverability — all auth code lives in features/auth/
2. Scalability — adding a feature means adding a folder, not scattering files
3. Team parallelism — multiple developers can work on different features without conflicts
4. Easy deletion — remove an entire feature by deleting one folder
5. Test organization — tests mirror the feature structure

Core vs Features

core/ contains shared utilities used across features:

• Theme definitions
• Network client setup
• Shared widgets
• Utility extensions

features/ contains feature-specific code organized by Clean Architecture layers.

Example: Auth Feature

features/auth/
├── domain/
│   ├── entities/
│   │   └── user.dart
│   ├── use_cases/
│   │   └── sign_in.dart
│   └── repositories/
│       └── auth_repository.dart
├── data/
│   ├── data_sources/
│   │   └── auth_api.dart
│   ├── models/
│   │   └── user_dto.dart
│   └── repositories/
│       └── auth_repository_impl.dart
└── presentation/
    ├── controllers/
    │   └── login_controller.dart
    └── screens/
        └── login_screen.dart

Module Exports

Use barrel files for clean imports:

// features/auth/auth.dart
export 'domain/entities/user.dart';
export 'presentation/screens/login_screen.dart';
export 'presentation/controllers/login_controller.dart';

Now other features import features/auth/auth.dart instead of deep paths.

When to Use Which

Approach	Best For
Type-based	Tiny prototypes, learning projects
Feature-based	Production apps, team projects
Hybrid	Medium apps with shared core + features

Conclusion

Feature-based structure is the industry standard for Flutter apps in production. Adopt it early, and your future self (and team) will thank you.