orbit-mvi
mobx
| orbit-mvi | mobx | |
|---|---|---|
| 6 | 1 | |
| 834 | 6 | |
| 2.3% | - | |
| 6.4 | 0.0 | |
| 11 days ago | over 3 years ago | |
| Kotlin | Kotlin | |
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
orbit-mvi
-
MVI with usecase instead of repository?
Go over to the docs for orbit-mvi and show how it has these flaws.
-
I ported the Spotify Mobius GitHub wiki to GitHub Pages + MkDocs with light and dark modes. I just created the issue and filed the PR. Let's see what happens!
This looks great! Semi-related question... have you evaluated other MVI frameworks like Mavericks / Uniflow / Orbit? What made you decide on Mobius?
-
Implementing Jetpack Compose + Orbit MVI
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
-
Compose architecture: MVVM or MVI with Flow?
Do you recommend Mavericks? I've been meaning to evaluate it and orbit-mvi.
-
What is wrong with MVVM?
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.
-
Why is there nothing like Redux, Vuex, MobX, etc... for Android?
Redux is called MVI in Android world. There are plenty of MVI libs: MVICore, orbit-mvi, mobius and other.
mobx
-
Why is there nothing like Redux, Vuex, MobX, etc... for Android?
There is also SamakaCD/mobx with true TFRP (Transparent functional reactive programming), but it looks abandoned.
What are some alternatives?
Jetpack-Compose-Orbit-MVI-Demo - Demo / Sample Android Project created with Jetpack Compose and Orbit MVI
workflow-kotlin - A Swift and Kotlin library for making composable state machines, and UIs driven by those state machines.
MVIKotlin - Extendable MVI framework for Kotlin Multiplatform with powerful debugging tools (logging and time travel)
compose-samples - Official Jetpack Compose samples.
MVICore - MVI framework with events, time-travel, and more
MVI-Coroutines-Flow - Play MVI with Kotlin Coroutines Flow | MVI pattern on Android using Kotlin Coroutines Flow | Dagger Hilt DI | Koin DI | SharedFlow | StateFlow | Arrow.kt Android Sample
mobius - A functional reactive framework for managing state evolution and side-effects.
MvRx - Mavericks: Android on Autopilot
Sesame - Android architecture components made right
livedata-combineutil-java - [ACTIVE] Helper function to combine LiveDatas.