Does this skill support Kotlin Multiplatform (KMP)?

Yes, it includes specific patterns for KMP projects, such as SQLDelight for local storage and Ktor for networking, designed for code sharing between Android and iOS.

Why shouldn't the domain layer depend on the data layer?

To ensure the business logic is independent of external factors like database types or network APIs, allowing you to swap out your data source without affecting core logic.

Which dependency injection frameworks are covered?

The skill provides implementation guidance for both Hilt (the standard for Android-only projects) and Koin (a popular choice for KMP and Kotlin-first projects).

What is the primary benefit of using Clean Architecture in Android?

It separates business logic from UI and framework code, making the application easier to test, maintain, and adapt to platform changes without breaking core logic.

Android Clean Architecture

Name: Android Clean Architecture
Author: hieuck

byhieuck

0•

Mobile Development

Implements modular Clean Architecture patterns for Android and Kotlin Multiplatform projects to ensure maintainability and testability.

This skill provides a comprehensive framework for structuring Android and Kotlin Multiplatform (KMP) applications using Clean Architecture principles. It guides the creation of clear module boundaries, enforces dependency inversion, and provides standardized templates for UseCases, Repositories, and DataSources. By integrating best practices for data persistence with Room or SQLDelight, networking via Ktor, and dependency injection with Hilt or Koin, it ensures that business logic remains decoupled from framework-specific implementation details.

Características Principales

01Data layer mapping strategies for Entities, DTOs, and Domain models

02Implementation patterns for UseCases using functional operator patterns

030 GitHub stars

04Dependency injection configuration for both Koin and Hilt frameworks

05Standardized multi-module project structure for Android and KMP

06Domain layer protection through strict dependency inversion rules

Casos de Uso

01Bootstrapping a new Kotlin Multiplatform project with scalable architecture

02Standardizing data flow patterns between remote APIs and local databases

03Refactoring existing Android code into testable Domain and Data layers

Características Principales

01Data layer mapping strategies for Entities, DTOs, and Domain models

02Implementation patterns for UseCases using functional operator patterns

030 GitHub stars

04Dependency injection configuration for both Koin and Hilt frameworks

05Standardized multi-module project structure for Android and KMP

06Domain layer protection through strict dependency inversion rules

Casos de Uso

01Bootstrapping a new Kotlin Multiplatform project with scalable architecture

02Standardizing data flow patterns between remote APIs and local databases

03Refactoring existing Android code into testable Domain and Data layers