android-clean-architecture

Structure Android clean architecture projects by organizing modules into app, core, domain, data, presentation, and feature layers to enforce separation of concerns and dependency rules. This modular layout improves testability, scalability, and maintenance across Android and Kotlin Multiplatform projects.

Implement UseCase and Repository patterns in Kotlin Multiplatform by defining repository interfaces in the pure domain layer and designing data flows between domain, data, and presentation layers. This approach keeps domain logic decoupled from frameworks while ensuring clean data flow.

Yes, the clean architecture guidance supports Room, SQLDelight, and Ktor for typical data-layer implementations. It provides practical patterns for integrating these specific frameworks within the data module while maintaining strict module boundaries.

Yes, you can use Hilt or Koin for dependency injection in a clean architecture Android project. The guidance includes DI integration to wire dependencies while keeping the domain layer pure and fully decoupled from frameworks.

The best way to enforce dependency inversion across Android and Kotlin Multiplatform modules is applying real-world patterns for structuring cross-platform modules. This ensures architectural constraints are met by pointing dependencies inward toward the pure domain layer.