Ross ROSS = Recommend OSS · open-source software intelligence for agents

icerockdev/moko-mvvm

Model-View-ViewModel architecture components for mobile (android & ios) Kotlin Multiplatform development observed · 2026-08-28

github.com/icerockdev/moko-mvvm · homepage · Kotlin · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

23/100

  • Activity 0
  • Release rhythm 8
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 2562
  • days_rel: n/a
  • days_push: 867
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

1097 stars · 97 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

moko-mvvm is a Kotlin Multiplatform library providing Model-View-ViewModel architecture components for mobile applications targeting Android and iOS. It offers lifecycle-aware ViewModels, LiveData/Flow reactive data holders, and an EventsDispatcher, with integration support for DataBinding, ViewBinding, Jetpack Compose, and SwiftUI.

Use cases

  • share viewmodel logic between android and ios in kotlin multiplatform
  • lifecycle-aware mvvm architecture for kotlin multiplatform mobile apps
  • reactive livedata or flow data holders in common kotlin code
  • dispatch ui events from viewmodel to view on both platforms
  • use viewmodels with jetpack compose multiplatform or swiftui
  • interop with androidx lifecycle viewmodel on android

When to choose

  • building a Kotlin Multiplatform Mobile app that needs shared presentation-layer architecture
  • you want ViewModel and LiveData/Flow semantics in common code with Android Architecture Components interop
  • you use the moko ecosystem (moko-resources, moko-fields, etc.) and want consistent MVVM support

When to avoid

  • building a single-platform Android app where plain AndroidX ViewModel and LiveData suffice
  • using a different multiplatform architecture approach like MVI (e.g., MVIKotlin, Decompose)
  • your project does not use Kotlin Multiplatform at all

Facets

library · maturity stable

state-management ui-components mobile-development cross-platform web-development jvm windows kotlin-multiplatform mvvm viewmodel livedata coroutines jetpack-compose swiftui databinding moko android ios macos linux

2 sources

Member repositories

RepositoryRoleHealth v2
icerockdev/moko-mvvmmain23

For agents

markdown · JSON · MCP: product_card(name="icerockdev/moko-mvvm")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem