clean-architecture

Structure a Kotlin Compose project by organizing it into presentation, domain, and data layers. This enforces clean separation of concerns by guiding repository interfaces, domain use cases, data mappers, and ViewModels across your MVVM-based apps.

Add a use case in the domain layer when you need to encapsulate specific business logic away from ViewModels and repositories. This maintains boundary integrity between presentation and data layers in your Kotlin app.

Yes, this approach specifically targets Kotlin and Compose Android projects using the MVVM pattern. It guides a presentation layer with Compose UI, ViewModels, and navigation while keeping domain models and repository interfaces explicitly separated from data mappers.

The best way to organize these layers is by defining explicit domain models, repository interfaces, and use cases in the domain layer, while employing data mappers in the data layer and ViewModels with Composables in the presentation layer to enforce strict module separation.

Data mappers fit into the data layer by translating remote or local data sources into explicit domain models. This ensures the domain layer remains independent of the data layer's implementation details in your Kotlin app.