android-clean-architecture

Structure an Android app using Clean Architecture by dividing it into domain, data, presentation, and core modules with strict dependency rules. This framework defines clear boundaries for UseCases, Repositories, and DataSources to ensure maintainability and testability.

The best way to implement Clean Architecture in KMP projects is by defining module structures and dependency rules that separate domain logic from platform-specific code. This approach uses SQLDelight for data persistence and Ktor for networking across shared modules.

Yes, you can use Hilt and Koin for dependency injection in a Clean Architecture Android app. This framework demonstrates setup with both Koin and Hilt to manage dependencies across your layered modules effectively.

Handle errors in UseCases and Repositories using Result or Try patterns. This approach encapsulates exceptions and failures within the domain and data layers, ensuring predictable error propagation without crashing the application.

Yes, this Clean Architecture framework supports both Room and SQLDelight for local data persistence. It demonstrates data layer integration using Room for standard Android projects and SQLDelight for Kotlin Multiplatform projects.