mvi-editor

MVI architecture enforces unidirectional data flow by passing user intents to a ViewModel, which then updates an immutable ViewState. This ensures predictable state management and makes Android UI components reactive and maintainable without external libraries.

Side effects in MVI are handled using a ViewEffect contract definition within your base ViewModel classes. This mechanism isolates one-time events like navigation or showing toasts from the continuous ViewState, ensuring they execute without triggering continuous UI recomposition.

Refactoring an existing ViewModel to MVI involves defining contract classes for ViewState, ViewEvent, and ViewEffect, then migrating logic into a base MVI ViewModel. This transitions your screen to unidirectional data flow and immutable state management.

You can use MVI architecture with both Jetpack Compose and traditional Android Views. The pattern provides base ViewModel classes and contract definitions that facilitate reactive UI integration across different Android UI toolkits.

You do not need external libraries to manage state with MVI in Kotlin. This approach provides a self-contained solution for state management and unidirectional data flow using base ViewModel classes and contract definitions.