android-clean-architecture

Structure an Android project with clean architecture modules by organizing your codebase into app, core, domain, data, and presentation layers. This enforces clear boundaries and dependency rules, keeping domain logic independent from data and presentation layers to ease maintenance.

The correct dependency rule for domain and data layers in Kotlin Multiplatform mandates that domain layers and UseCases remain completely independent of data and presentation layers. This separation ensures data layer implementations can change without affecting core business logic.

Yes, you can use Koin or Hilt for dependency injection across clean architecture modules. The Skill provides practical DI guidance to configure injections across app, domain, and data layers, supporting both Koin for KMP projects and Hilt for standard Android applications.

Implement a UseCase and Repository pattern in Android clean architecture by defining interfaces like GetUserProfileUseCase in the domain layer, then providing concrete data layer implementations using repositories. This pattern isolates business rules from data sources.

Clean architecture for Kotlin Multiplatform works seamlessly with Room, SQLDelight, and Ktor. The data layer design supports these frameworks for database management and network requests, allowing you to map external data sources directly to domain models.

You should not use clean architecture for your Android app when dealing with small, prototype-level projects where strict module separation and UseCase patterns introduce unnecessary overhead. It is designed to ease maintenance and scaling for complex applications.