android-clean-architecture

Structure an Android app with clean architecture by organizing modules into domain, data, and presentation layers. Apply strict dependency rules to enforce domain purity, ensuring the domain layer remains Kotlin-only with no data or presentation dependencies.

The domain layer in clean architecture needs to be Kotlin-only to enforce framework independence. This purity ensures domain logic remains free of data or presentation dependencies, allowing the core business rules to be shared across Android and Kotlin Multiplatform projects.

Yes, this clean architecture approach works with Kotlin Multiplatform and SQLDelight. It prescribes module boundaries and data-layer implementations for KMP projects, supporting data sources like SQLDelight and Ktor alongside standard Android tools like Room.

The best way to set up dependency injection for Android clean architecture is using Koin or Hilt. The architecture provides specific guidance on integrating these DI frameworks within the layered domain, data, and presentation module boundaries.

Implement the Repository and UseCase patterns by defining domain models and applying data mapping across layers. This approach ensures clean data flow from the data layer through the domain layer, keeping business logic isolated and maintainable.