How kotlin-android-open-source/mvi-coroutines-flow works
Project type and purpose
• This is a multi-module Android application showcasing Clean Architecture with MVI (Model-View-Intent) built on Kotlin, Coroutines, Flow, and ArrowKt.
• It’s composed of:
• A top-level “app” module (the Android host)
• Core common modules (core-ui, core, mvi-base, mvi-testing, test-utils)
• Domain and data layers (domain, data)
• Feature modules (feature-main, feature-add, feature-search)
• Build support (buildSrc, Gradle wrappers)
File structure
• Top-level gradle files and settings.gradle.kts wire up all modules.
• “app” depends on all feature modules plus core-ui, data, domain, etc., and contains the AndroidManifest and resource overlays.
• “core” contains pure Kotlin utilities: EitherNes, dispatchers, mappers.
• “core-ui” holds reusable UI bindings and navigation abstractions.
• “domain” defines your UseCases and Repository interface.
• “data” provides the UserRepositoryImpl, Retrofit API service, mappers, and error models.
• “feature-*” modules implement MVVM/MVI presentation: Contract, ViewModel (VM), Module (DI), Activity or Adapter, layouts, tests.
• “mvi-base” supplies abstract Activity/VM/ViewState/Intent/Event classes.
• “mvi-testing” & “test-utils” offer test rules, fake dispatchers, base test classes.
README for additional insights
• Explains your MVI cycle: intent() → model() → view().
• Mentions Clean Architecture layering, ArrowKt for functional programming, and Koin DI (with an obsolete Dagger Hilt branch).
• Shows your CI badges, minimum API level, and sample screenshots.