android-clean-architecture

Structure an Android app using clean architecture by dividing it into app, core, domain, data, and presentation modules. This approach enforces module boundaries, ensures domain purity, and maintains clear data flow across UseCase and Repository patterns.

Dependency rules for a pure domain layer require it to remain completely independent from the data and presentation layers. This separation ensures domain purity, keeping business logic isolated from data sources like Room or SQLDelight.

You can use either Koin or Hilt for dependency injection in a modular Android project. The clean architecture pattern supports DI configurations for both frameworks to manage dependencies across feature and data layers.

Implement offline support and data synchronization by utilizing a clean domain layer with Repository and DataSource patterns. This setup manages local data via Room or SQLDelight and remote interactions via Ktor for seamless synchronization.

The best way to organize feature modules is to follow a strict module layout that isolates features while routing dependencies through core modules. This maintains clear separation of concerns and structured data flow.