android-clean-architecture

Android clean architecture organizes modules into app, core, domain, data, presentation, and feature layers. This structure enforces dependency inversion and separates domain logic from data and UI, improving testability and maintainability across your project.

Android clean architecture requires the domain layer to never depend on data or UI modules. The app depends on presentation, domain, data, and core, while the data layer depends on domain interfaces, enforcing strict dependency inversion.

Yes, clean architecture applies to both Android apps and Kotlin Multiplatform projects. It structures shared KMP code using domain models, repository interfaces, and UseCase patterns to ensure testability and maintainability across platforms.

Implement the domain layer using the UseCase pattern, domain models, and repository interfaces. This isolates core business logic from data sources and UI frameworks, maintaining strict separation of concerns and improving testability.

Yes, the data layer integrates with dependency injection frameworks like Koin or Hilt. DI wiring connects repository implementations and data sources to domain layer interfaces, completing the dependency inversion setup for your Android app.

The data layer provides repository implementations and data sources that fulfill the domain layer's repository interfaces. Without it, UseCases cannot retrieve or persist data, breaking the dependency inversion required by clean architecture.