From 2193565071f81bbec4e92111353b22424f840c13 Mon Sep 17 00:00:00 2001 From: Brian Rodriguez Date: Thu, 12 Sep 2024 05:04:16 -0500 Subject: [PATCH] Add docs: Android mvi (#7086) * [Add] MVI docs * [Add] Format & add link * Update src/data/roadmaps/android/content/mvi@Bz-BkfzsDHAbAw3HD7WCd.md cleaned --------- Co-authored-by: dsh --- .../android/content/mvi@Bz-BkfzsDHAbAw3HD7WCd.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/src/data/roadmaps/android/content/mvi@Bz-BkfzsDHAbAw3HD7WCd.md b/src/data/roadmaps/android/content/mvi@Bz-BkfzsDHAbAw3HD7WCd.md index e69de29bb..b20724ef1 100644 --- a/src/data/roadmaps/android/content/mvi@Bz-BkfzsDHAbAw3HD7WCd.md +++ b/src/data/roadmaps/android/content/mvi@Bz-BkfzsDHAbAw3HD7WCd.md @@ -0,0 +1,11 @@ +# MVI + +The **MVI** `Model-View-Intent` pattern is a reactive architectural pattern, similar to **MVVM** and **MVP**, focusing on immutability and handling states in unidirectional cycles. The data flow is unidirectional: Intents update the Model's state through the `ViewModel`, and then the View reacts to the new state. This ensures a clear and predictable cycle between logic and the interface. + +- Model: Represents the UI state. It is immutable and contains all the necessary information to represent a screen. +- View: Displays the UI state and receives the user's intentions. +- Intent: The user's intentions trigger state updates, managed by the `ViewModel`. + +Visit the following resources to learn more: + +- [@article@MVI with Kotlin](https://proandroiddev.com/mvi-architecture-with-kotlin-flows-and-channels-d36820b2028d)