android-clean-architecture

Structure Android projects by defining clear module boundaries between app, domain, data, and presentation layers. This enforces separation of concerns and establishes explicit dependency rules to prevent framework components from polluting the domain layer.

Yes, clean architecture applies to Kotlin Multiplatform projects to define module boundaries, UseCases, repositories, and data layer patterns. It enforces domain-layer purity by keeping shared modules independent of platform-specific UI or framework components.

Enforce dependency rules by structuring modules so the domain and data layers never depend on UI or framework components. This maintains a pure domain layer and ensures data layer patterns respect strict module boundaries for better testability.

Yes, it provides dependency injection guidance for both Koin and Hilt. This ensures your modular Android architecture correctly wires together UseCases, repositories, and DataSources across the app, domain, and data layers.

Organize UseCases and Repositories by placing them within defined domain and data layer boundaries. This separation of concerns promotes testability and ensures data layer patterns remain decoupled from the presentation layer.

Avoid clean architecture if your Android app is extremely small, as enforcing strict module boundaries, UseCases, and dependency rules introduces unnecessary structural overhead for simple projects that do not require high separation of concerns.