android-clean-architecture

Clean architecture for Android and Kotlin Multiplatform projects separates code into structured layers with strict dependency rules, defining module layouts, UseCases, and Repositories to isolate business logic from data persistence and UI frameworks.

To structure Android modules using clean architecture, apply a recommended layout that enforces dependency rules across layers, separating UseCases for business operations from the data layer handling network requests and database persistence.

Yes, this clean architecture approach works with both Koin and Hilt for dependency injection, offering specific setup instructions and patterns to inject dependencies across different modules in Android and Kotlin Multiplatform apps.

Yes, you can use Room and SQLDelight in the same Kotlin Multiplatform data layer. The architecture guidelines cover designing and implementing data persistence operations using both database frameworks alongside Ktor for network operations.

The best way to handle errors in Android clean architecture is by implementing Result and Try patterns. These provide robust error handling mechanisms to manage failures across UseCases, Repositories, and data layer operations.

You need UseCases and Repositories in your Android module structure when isolating business operations and data persistence. UseCases handle specific business logic, while Repositories manage data access from Room, SQLDelight, or Ktor network sources.