mobius VS Sesame

But they used https://github.com/spotify/mobius a while ago.

👋 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 ❤️🔥

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

If you are looking for a paging library take a look at https://github.com/aartikov/Sesame/tree/master/sesame-loading

I use property delegate that wraps MutableStateFlow. This solution results in minimum of boilerplate code:

My Sesame-property is inspired by MobX. It provides observable mutable properties for core state and observable computed properties for derived state.

My library Sesame Activable works exactly as you described.

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

Hi. I have developed a library called Sesame.