android-clean-architecture

Clean architecture for KMP involves separating domain, data, and presentation layers. This Skill guides you in defining module boundaries, creating domain use cases, and implementing repository interfaces to ensure your multiplatform codebase remains modular and testable.

The best way to implement the domain layer in Kotlin Multiplatform is by creating UseCases, domain models, and repository interfaces. This approach isolates your business logic from the data and presentation layers, making your core application logic highly testable and maintainable.

You implement the data layer in clean architecture by creating repository implementations that fetch data from local databases like Room or SQLDelight, and remote sources using Ktor network clients, mapping them to domain models.

Yes, you can use Hilt and Koin for dependency injection across clean architecture modules. This Skill provides demonstrations on configuring both DI frameworks to supply dependencies effectively across the domain, data, and presentation layers in Android and KMP projects.

To handle errors in Kotlin clean architecture, implement best practices using Result and Try patterns. This approach propagates failures safely across architectural boundaries without throwing exceptions, ensuring robust error handling within your UseCases and repository implementations.

Common anti-patterns to avoid in Android clean architecture include leaking data layer details into the domain layer and bypassing repository interfaces. This Skill provides tips to identify and avoid these architectural mistakes, preserving strict module separation and testability.