Short summary of this really well written article:
Pattern overview
MVP, MVVM, and MVI are some of the common patterns in Android and they can broadly be thought of as different flavours of the same core concept — abstracting logic from the UI into classes without references to Android. The main way in which they differ is how those classes accept their inputs and how they then output updates to the UI.
The defining feature of MVP is that data is communicated back to the view imperatively.
MVVM
MVVM differs from MVP is in how data is communicated back to the view. Rather than imperatively calling the view, in MVVM changes are described by data which are then observable by the view. The UI can then reactively re-compose itself based on the new data.
MVI
This is a very similar pattern to MVVM, with some important differences. In many ways it’s a merging of MVVM & Redux. MVI pre-defines a selection of events the ViewModel handles and the view publishes a stream of these events as they happen. But the major difference is communication back to the view. Whereas in MVVM there is usually a separate publisher for each piece of data, in MVI a single object defining the entire state of the view is published. Often there’s a section of MVI which follows Redux style reducing.
*update December 2025: I'm visualizing the data at https://storage. services. kibotu. net/geiger now. After watching HBO's Chernobyl Series and stumbling upon this awesome article about someone building a steampunk desktop background radiation monitor I… more
Finally a live event again. 95 tech talks, 5 simultaneously for 3 days, 1200+ Android Developers, 87 Speaker by over 50 different companies participated. Topics ranged from `new` technologies, e.g. Jetpack Compose, KMM to how to improve productivity… more
