android-clean-architecture

This Skill provides guidelines for implementing clean architecture in Android by defining module boundaries, dependency rules, UseCase patterns, and data layer designs to improve project maintainability and scalability.

Setting up dependency injection with Koin or Hilt in Kotlin Multiplatform involves configuring specific Gradle plugins and following module boundary rules. This ensures proper dependency management across shared and platform-specific modules.

The best way to handle errors in Android clean architecture is using the Result or Try pattern for error propagation. This mechanism safely manages failures across data and domain layers without breaking application flow.

Yes, you need existing knowledge of Android development, Kotlin, and multiplatform development tools. This background is required to effectively implement the module structures, convention plugins, and repository patterns provided.

Common anti-patterns to avoid in Android clean architecture include violating dependency rules between modules and mismanaging repository implementations. Reviewing these mistakes ensures your application structure remains maintainable and scalable.

Configuring Gradle convention plugins for a Kotlin Multiplatform clean architecture project involves setting up specific module structures and dependency rules. This standardizes build configurations across your shared and platform-specific modules.