MVIKotlin VS orbit-mvi

Full discretion, all my new apps are built using mvi with MVIKotlin and decompose for the compose extensions for navigation animations. A sample project I have built with that architecture can be found here.

If you're looking at using MVI with kotlin in general, you should check out MVIKotlin. It provides the basic rails for the pattern with support for coroutines and reaktive.

There's also MVIKotlin.

Project page: https://github.com/arkivanov/MVIKotlin

Go over to the docs for orbit-mvi and show how it has these flaws.

This looks great! Semi-related question... have you evaluated other MVI frameworks like Mavericks / Uniflow / Orbit? What made you decide on Mobius?

Name Link Koin https://insert-koin.io Jetpack Compose https://developer.android.com/jetpack/compose Navigation Compose https://developer.android.com/jetpack/compose/navigation Orbit MVI https://orbit-mvi.org Coil https://coil-kt.github.io/coil/ Room https://developer.android.com/training/data-storage/room?hl=ja Kotlin-Serialiazation https://github.com/Kotlin/kotlinx.serialization PokemonGO-Pokedex https://github.com/Biuni/PokemonGO-Pokedex

Do you recommend Mavericks? I've been meaning to evaluate it and orbit-mvi.

Everything in MVI is just more code that does nothing (see how most MVI frameworks are basically just a wrapper over state.value = state.copy() like in Orbit or MvRx which you wouldn't even need if you used combiners) and instead adds unnecessary constraints over MVVM that don't help you at all. The "sealed class inputs" are basically a reinvention of calling interface functions except you create classes for it, despite there being no asynchronicity when you have a View -> ViewModel communication.

Redux is called MVI in Android world. There are plenty of MVI libs: MVICore, orbit-mvi, mobius and other.