MvRx VS uniflow-kt

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!

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

bruh no if you just call the api and show the results instead of wrapping it in a repository and wrapping it in a usecase and wrapping it into a helper then people might think you're doing trivial stuff, how can you show off with super-smart-looking code if 1 function call doesn't require 4 classes that do nothing or a framework that does nothing