Where to Go From Here?
In this tutorial, you learned the key points of MVI, including:
In summary, MVI is a powerful architecture pattern. It relies on a unidirectional data flow and immutable Models to solve common concerns across Android development such as the state problem and thread safety.
To learn more about RxJava, check out the official ReactiveX website for the documentation and many useful examples.
I also recommend our Advanced Android app Architecture book, which contains three full chapters about MVI as well as other popular architecture patterns such as MVC, MVP, MVVM and VIPER.
Finally, we also have video courses on MVP, MVVM, and MVI. The video courses build a complete app using each of the different patterns.
Feel free to share your feedback or ask any questions in the comments below or in the forums!
-
MVI stands for Model-View-Intent
-
Models in MVI represent a state of an app.
- A state represents how an app behaves or reacts at any given moment such when loading screen or displaying new data in a list or a network error.
-
Views in MVI can have one or more
intent()s that handle user actions and a single render() that renders the state of your app.
- The Intent represents an intention to perform an action by the user like an API call or a new query in your database. It does not represent the usual
android.content.Intent
-
Reducer functions provide steps to merge things into a single component called the accumulator.
- MVI provides a unidirectional and cyclical data flow.
