Sesame
Android architecture components made right (by aartikov)
mobius
A functional reactive framework for managing state evolution and side-effects. (by spotify)
Sesame | mobius | |
---|---|---|
7 | 3 | |
109 | 1,207 | |
- | 0.4% | |
0.0 | 6.1 | |
about 2 years ago | 3 days ago | |
Kotlin | Java | |
MIT License | Apache License 2.0 |
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.
mobius
Posts with mentions or reviews of mobius.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-14.
-
Spotify app architecture
But they used https://github.com/spotify/mobius a while ago.
-
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!
👋 I have been using Mobius personally and for work for over two years now. It's a lot of fun to use and I would definitely recommend the community to consider using it. I frequently visit their GitHub repo because they still have their documentation in the GitHub wiki, unlike new repos such as Accompanist. So, I thought what better way to give back than do the grunt work of porting their wiki to GitHub Pages + MkDocs ❤️🔥
-
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.
What are some alternatives?
When comparing Sesame and mobius you can also consider the following projects:
MVICore - MVI framework with events, time-travel, and more
orbit-mvi - A simple MVI framework for Kotlin Multiplatform and Android
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.