Sesame
Android architecture components made right (by aartikov)
MVICore
MVI framework with events, time-travel, and more (by badoo)
| Sesame | MVICore | |
|---|---|---|
| 7 | 3 | |
| 109 | 1,217 | |
| - | 0.6% | |
| 0.0 | 5.2 | |
| about 2 years ago | 27 days ago | |
| Kotlin | Kotlin | |
| MIT License | GNU General Public License v3.0 or later |
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.
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.
MVICore
Posts with mentions or reviews of MVICore.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-04-14.
-
Bumble claims IP rights on employee's open-source libs
> ... commercial software ...
Commercial and OSS are orthogonal.
> ... that is private
It seems to have been released under Apache 2.0: https://github.com/badoo/MVICore/blob/master/LICENSE
> The company _could_ make it OSS
They _did_
-
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.
-
MVI: Safe ways to delegate render methods from Fragments
In this case maybe you should diff your view state and render only parts that have changed. I have written a diff-dispatcher library to help with this, but there's now a better one from badoo guys which doesn't need kapt.
What are some alternatives?
When comparing Sesame and MVICore you can also consider the following projects:
compose-samples - Official Jetpack Compose samples.
orbit-mvi - A simple MVI framework for Kotlin Multiplatform and Android
workflow-kotlin - A Swift and Kotlin library for making composable state machines, and UIs driven by those state machines.
mobius - A functional reactive framework for managing state evolution and side-effects.
Flywheel - A simple and predictable state management library inspired by Redux for Kotlin Multiplatform using the concepts of actors.