android-clean-architecture

Structure an Android app by separating it into domain, data, and presentation layers. This modular approach enforces clear module boundaries and dependency rules, ensuring use cases, repositories, and data sources remain decoupled for better maintainability.

The recommended module layout for a Kotlin Multiplatform project separates code into app, core, domain, data, presentation, and design-system modules. This separation enforces strict dependency rules and clarifies boundaries between shared logic and platform-specific UI.

Configure dependency injection with Koin or Hilt by aligning DI modules with clean architecture layers. Wire use cases, repository interfaces, and data sources into their respective domain and data layers to preserve separation of concerns.

Yes, you can apply clean architecture to both Android and Kotlin Multiplatform projects. The approach defines domain and data layer patterns, like repositories and use cases, that work across platforms while maintaining strict module boundaries and dependency rules.

Enforce dependency rules between domain and data layers whenever you structure an Android app to prevent presentation and data layers from directly coupling to domain logic. This ensures repositories and use cases remain independently testable and maintainable.