android-clean-architecture

To structure Android projects with clean architecture, separate your code into domain, data, and presentation layers. This layered approach enforces strict dependency rules, ensuring the domain layer remains independent of data, presentation, and framework modules for better testability and scalability.

The recommended module layout for scalable Kotlin Multiplatform apps includes separate app, core, domain, data, presentation, and design-system modules. This structure enforces clear boundaries and dependency rules between layers to maintain testability and maintainability as the project grows.

Wire UseCases and Repositories using dependency injection frameworks like Hilt or Koin. You connect UseCases to their corresponding Repositories in the presentation layer, ensuring clean data flows and maintaining strict separation between the domain and data layers.

Yes, clean architecture for Android works with Room and SQLDelight by implementing a layered data architecture. These database frameworks reside in the data layer, keeping data mapping and storage separate from the domain layer which holds your UseCases and Repositories.

You should avoid clean architecture for small or simple Android apps where the overhead of maintaining strict module boundaries and multiple layers outweighs the benefits. It is designed for scalable projects requiring high testability, maintainability, and clear separation of concerns.