android-clean-architecture

Enforce module boundaries in Android Kotlin projects by defining explicit dependency rules across app, domain, data, and presentation layers, ensuring the domain layer never depends on data or presentation modules. This separation promotes testability and prevents tight coupling.

Structure clean architecture layers by separating Domain logic with UseCases and Repositories from the Data layer containing data sources. This pattern ensures domain models remain independent of data implementations like Room or SQLDelight, maintaining clear separation of concerns.

Kotlin Multiplatform supports clean architecture by organizing Domain, Data, and presentation modules with shared logic. It integrates with SQLDelight and Ktor for the data layer while keeping domain UseCases platform-agnostic and fully testable across targets.

Wire dependency injection across Android modules using Hilt or Koin to provide UseCases, Repositories, and DataSources to the presentation layer. This setup ensures modules remain decoupled while facilitating easy testing and modular component provisioning.

The domain layer must not depend on the data layer to protect business logic from external changes like database or API swaps. Keeping domain models and UseCases independent ensures core rules remain testable and reusable across different data source implementations.