android-clean-architecture

Android clean architecture structures projects into domain, data, and presentation layers with strict dependency rules. Presentation and data depend on domain, but domain never depends on frameworks, ensuring testable business logic and clear module boundaries.

Isolate Room and Ktor data sources by defining repository interfaces in the domain layer. Implement these in the data layer using Room for Android or SQLDelight for KMP, mapping network and database results consistently to pure Kotlin domain models.

Yes, this clean architecture approach supports both Koin and Hilt for dependency injection. It provides implementation guidance for wiring your UseCases, repositories, and data sources across the domain, data, and presentation layers using either DI framework.

Handle errors in UseCases using Result or Try-style propagation. This approach enforces consistent error handling across module boundaries, ensuring repository failures from Ktor or Room are mapped cleanly without breaking pure Kotlin domain constraints.

Enforce pure Kotlin domain constraints by ensuring the domain layer never depends on frameworks or data details. Define UseCases and repository interfaces using pure Kotlin, keeping all Room, SQLDelight, and Ktor implementations strictly in the data layer.