android-clean-architecture

To structure an Android project with Clean Architecture, you separate domain, data, and presentation layers while enforcing strict dependency rules. The domain layer stays framework-free by defining repository interfaces and UseCases, keeping Android dependencies isolated in the outer layers.

Setting up Gradle convention plugins for a Kotlin Multiplatform Clean Architecture project standardizes module configurations. This approach generates reproducible builds by centralizing dependency directions and KMP module setups, ensuring architectural rules are enforced across shared code.

Implementing the Repository pattern with Room and Ktor involves defining repository interfaces in the domain layer. The data layer then coordinates local Room or SQLDelight data sources with remote Ktor clients, applying data mapping strategies to return domain models.

You can use Koin or Hilt for dependency injection in a Kotlin Multiplatform Clean Architecture setup. Koin is fully KMP compatible, while Hilt integrates specifically with the Android presentation layer, allowing you to wire ViewModels and data source implementations effectively.

Exposing data with Flow and coroutines from UseCases in a Clean Architecture module involves returning reactive streams from repository interfaces. UseCases invoke these repositories and propagate Flow patterns to the presentation layer, ensuring asynchronous data operations remain testable.

Using SQLDelight instead of Room for Kotlin Multiplatform Clean Architecture features enables shared database logic across platforms. SQLDelight provides KMP-compatible schemas, while Room is primarily Android-focused, making SQLDelight the better choice for cross-platform data layers.