android-clean-architecture

Structure Android apps by dividing them into domain, data, and presentation layers. Enforce clear module boundaries, apply dependency rules, and implement UseCase and Repository patterns to decouple business logic from UI frameworks.

Separate domain and data layers by defining strict dependency rules where the domain layer remains independent. Use repository patterns to handle data operations, ensuring the domain layer stays platform-agnostic for Kotlin Multiplatform compatibility.

Clean architecture integrates with dependency injection frameworks like Hilt or Koin. The structure provides specific guidance on DI integration to manage dependencies across the domain, data, and presentation layers without violating module boundaries.

Organize UseCase and Repository patterns by placing repositories in the data layer to fetch data, and UseCases in the domain layer to execute single business logic operations. This separation enforces unidirectional data flow across module boundaries.

Enforce strict module boundaries when an Android project grows large and tangled dependencies make maintenance difficult. Applying clean architecture early prevents inconsistent module structures and simplifies extending the app's features over time.

Clean architecture guidelines apply seamlessly to both standard Android and Kotlin Multiplatform apps. The module structure, dependency rules, and UseCase/Repository patterns are designed to support shared codebases across multiple platforms.