android-clean-architecture

Structure an Android Kotlin project using clean architecture by organizing it into domain, data, and presentation modules. This separation enforces dependency rules, keeping the domain layer pure while delegating data sources and UI interactions to their respective layers.

UseCases and Repositories in Android clean architecture define the domain layer's business logic and data contracts. UseCases orchestrate operations, while repository interfaces abstract data sources, ensuring core logic remains testable and independent of platform-specific implementations.

Yes, this clean architecture approach works with Kotlin Multiplatform projects. It provides specific guidance for platform-specific implementations and dependency rules, allowing you to share pure domain logic and data layer abstractions across different platforms effectively.

Yes, you can use Hilt or Koin for dependency injection in an Android clean architecture setup. The approach includes specific guidance for integrating DI frameworks to manage dependencies across your domain, data, and presentation modules seamlessly.

You should separate domain and data layers in your Android app when you need to improve modularity, testability, and maintainability. A pure domain layer with mapping utilities ensures your business rules are isolated from data source changes and UI concerns.