android-clean-architecture

Clean architecture structures Android and Kotlin Multiplatform projects into domain, data, presentation, and core layers. This modular layout defines clear dependency rules between modules to ensure maintainability and separation of concerns.

Implement the Repository pattern by wrapping local data sources like Room and SQLDelight alongside remote sources using Ktor. The repository coordinates these sources to provide a single data access point for your domain layer.

Both Koin and Hilt are supported for dependency injection in Android clean architecture projects. Koin offers a Kotlin-first approach, while Hilt provides compile-time safety, allowing you to choose based on your project's specific needs.

UseCases in the domain layer encapsulate single business logic operations. They orchestrate data flow by calling repositories, keeping your application logic isolated from both the UI and data implementation details.

The best way to handle errors in Kotlin clean architecture is using the Result or Try pattern. This approach safely propagates exceptions across module boundaries, allowing the presentation layer to manage failures gracefully.

Common clean architecture anti-patterns in Android include leaking data layer details into the domain and bypassing UseCases for business logic. Following strict module dependency rules prevents these architectural violations.