android-clean-architecture

Structure Android or Kotlin Multiplatform clean architecture by defining strict module boundaries across core, domain, data, and presentation layers. Enforce unidirectional dependency rules where domain depends on core, while data and presentation depend on domain to separate concerns.

Dependency rules for Android clean architecture enforce a strict unidirectional graph: data and presentation layers depend on the pure domain layer, which only depends on core. This constraint ensures the domain remains framework-agnostic and highly testable.

Organize UseCases and Repositories within the pure domain layer of your Kotlin Multiplatform app. Repositories define data contracts, while UseCases encapsulate single business operations, coordinating data flow between presentation and data layers.

Yes, this clean architecture pattern supports Room, SQLDelight, and Ktor stacks. It provides specific examples for integrating these frameworks within the data layer as DataSources while maintaining strict separation from the domain and presentation layers.

Use a multi-module clean architecture setup for Android apps when you need to improve testability and maintainability at scale. It helps teams enforce dependency rules and manage complex data flow across domain, data, and presentation layers.

Wire dependency injection across modules by providing data layer implementations like Repositories and DataSources from the presentation or app layer. This satisfies the unidirectional dependency graph, injecting dependencies into domain UseCases without coupling them to frameworks.