mobius VS MvRx

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.

you might find airbnb/mavericks familiar, because i think it has similar principles & api surface to felangel/cubit

This looks great! Semi-related question... have you evaluated other MVI frameworks like Mavericks / Uniflow / Orbit? What made you decide on Mobius?

https://airbnb.io/mavericks/#/jetpack-compose?id=creating-a-mavericksviewmodel

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.

Airbnb doesn't use MVI, we use MVVM via https://github.com/airbnb/mavericks

Check out the latest dagger sample from the repo. Dagger recently added assisted injection into the core library so you can now integrate the two without adding assisted inject!