# Reactive State Management with Model-View-Intent

DevFeed: [Reactive State Management with Model-View-Intent](<https://devfeed.tech/articles/reactive-state-management-with-model-view-intent-25476.md>)

Original publisher: [Read original article](<https://hannesdorfmann.com/presentations/2018-10-22-reactive-statemanagement-mvi/>)

Author: Hannes Dorfmann

Published: 2017-10-05T00:00:00Z

Content type: tutorial

Language: en

Sources: [Hannes Dorfmann](<https://devfeed.tech/sources/hannes-dorfmann.md>)

Topics: [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Android](<https://devfeed.tech/topics/android.md>), [reactive](<https://devfeed.tech/topics/reactive.md>), [RxJava](<https://devfeed.tech/topics/rxjava.md>), [Redux](<https://devfeed.tech/topics/redux.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [flow](<https://devfeed.tech/tags/flow.md>), [mvi](<https://devfeed.tech/tags/mvi.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [rxjava](<https://devfeed.tech/tags/rxjava.md>), [state-management](<https://devfeed.tech/tags/state-management.md>)

## AI overview

A presentation explains Model-View-Intent (MVI) as an architectural pattern for managing application state on Android. It covers synchronous and asynchronous data, component lifecycles, navigation, process death, comparisons with Flux and Redux, and unidirectional data flow with RxJava.

## Source excerpt

Managing application state is not a simple topic especially on Android with a synchronous and asynchronous source of data, components having different lifecycles, back stack navigation and process death. Model-View-Intent (MVI) is an architectural design pattern to separate the View from the Model. In this talk, we will discuss the idea behind MVI and how this pattern compares to other architectural patterns like Flux, Redux, Model-View-Presenter or Model-View-ViewModel.