MvRx VS architecture-samples

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?

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

Here's an example project on GitHub that demonstrates how to use a ViewModel in practice: https://github.com/android/architecture-samples/tree/master/BasicSample

For me this one is the best: Architecture samples it's easy to understand and covers lots of concepts.

For merging multiple data-sources, like network and database, I can use Repository backed with NetworkDataSources and DbDataSources. For data manipulation, Kotlin's collection has many useful functions (map, reduce, groupBy, count, etc.). If I want to ensure a data can only be emitted once, a simple modification to LiveData is enough (SingleLiveData

There are multiple ways to communicate UI state changes from your view model to the view like using LiveData and SingleLiveEvent (a specialized LiveData which can only be consumed once).

In Android we have a set of API which is part of the framework itself that helps us write code in MVVM-ish style. They have opinionated sample codes that works around these API as well: https://github.com/android/architecture-samples