android-clean-architecture

To structure an Android project with clean architecture, you organize code into app, core, domain, data, and presentation modules. This enforces dependency rules where the domain layer remains independent, while data and presentation layers depend on it to reduce coupling and improve maintainability.

Clean architecture keeps the domain layer framework-agnostic in Kotlin Multiplatform by representing UseCases as operator overloaded calls and keeping domain models pure Kotlin. This ensures the domain layer remains independent and prevents leakage of implementation details.

Yes, you can use Hilt or Koin for dependency injection in an Android clean architecture setup. The architecture provides specific patterns for DI wiring, allowing you to integrate either framework to support scalable and testable code across your modules.

The best way to implement Repositories and DataSources with Room and Ktor is by placing them in the data layer, which depends on the domain and core layers. This data-layer pattern supports integrations like Room, SQLDelight, and Ktor while maintaining strict separation of concerns.

You need to separate presentation and design-system modules in Android clean architecture when you want to organize UI responsibilities distinctly. The presentation layer depends on domain, design-system, and core layers, ensuring implementation details do not leak across module boundaries.

Yes, clean architecture for Android fully supports Kotlin Multiplatform projects. It provides a practical blueprint for structuring shared modules, defining data flow, and establishing testability across platforms while keeping the domain layer pure Kotlin.