orbit-mvi
A simple MVI framework for Kotlin Multiplatform and Android (by orbit-mvi)
Sesame
Android architecture components made right (by aartikov)
| orbit-mvi | Sesame | |
|---|---|---|
| 6 | 7 | |
| 834 | 109 | |
| 1.9% | - | |
| 6.4 | 0.0 | |
| 11 days ago | about 2 years ago | |
| Kotlin | Kotlin | |
| Apache License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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
Posts with mentions or reviews of orbit-mvi.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-14.
-
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.
Sesame
Posts with mentions or reviews of Sesame.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-04-14.
-
Do you guys feel like Jetpack Paging3 library messes with your Architecture a lot?
If you are looking for a paging library take a look at https://github.com/aartikov/Sesame/tree/master/sesame-loading
-
What's your way to expose an immutable StateFlow / LiveData from your ViewModel without bloating up your code?
I use property delegate that wraps MutableStateFlow. This solution results in minimum of boilerplate code:
-
Why is there nothing like Redux, Vuex, MobX, etc... for Android?
My Sesame-property is inspired by MobX. It provides observable mutable properties for core state and observable computed properties for derived state.
-
A safer way to collect flows from Android UIs
My library Sesame Activable works exactly as you described.
-
Sesame - Android architecture library
Sesame has a navigation component. But this one is supposed to be minimalistic. While Alligator has all the navigation implementation out of the box (passing screen arguments, controlling fragment backstack, animations and so on) Sesame provides only a way to deliver navigation messages. Both approaches has cons and pros. I personally will start my new project with Sesame navigation and copy-pasting some simple navigator like that FragmentNavigator.kt
-
Sesame - Android architecture components made right
Hi. I have developed a library called Sesame.
What are some alternatives?
When comparing orbit-mvi and Sesame you can also consider the following projects:
Jetpack-Compose-Orbit-MVI-Demo - Demo / Sample Android Project created with Jetpack Compose and Orbit MVI
MVICore - MVI framework with events, time-travel, and more
MVIKotlin - Extendable MVI framework for Kotlin Multiplatform with powerful debugging tools (logging and time travel)
compose-samples - Official Jetpack Compose samples.
workflow-kotlin - A Swift and Kotlin library for making composable state machines, and UIs driven by those state machines.
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
mobx - Kotlin MobX implementation
MobX - Simple, scalable state management.