Standardize Android/KMP screen logic with an MVI loop of State, Action, and Event.
npx skills add https://github.com/soygabimoreno/Los-ANDROIDES --skill android-mvi
Please help me install this Agent Skill. Skill: android-mvi Source: https://github.com/soygabimoreno/Los-ANDROIDES/tree/main/.agents/skills/android-mvi Command: npx skills add https://github.com/soygabimoreno/Los-ANDROIDES --skill android-mvi
It solves the confusion and bugs caused by inconsistent UI state handling by standardizing how Android/KMP screens manage State, Actions (Intents), and one-time Events.
Use the android-mvi skill to design a new screen by defining its <Screen>State, <Screen>Action, <Screen>Event, implementing a <Screen>ViewModel with Channel.BUFFERED events, and splitting UI into <Screen>Root and <Screen>Screen composables.
High-intent search queries and answers about installing and using this skill.
To handle one-time UI events safely, emit them through a Channel.BUFFERED and collect them lifecycle-aware via ObserveAsEvents, ensuring each event is consumed exactly once. This prevents duplicate side effects like repeated navigation or snackbar messages on configuration changes.
The best way to structure MVI is by defining State as the single source of UI data, Action as user inputs, and Event for side effects, processed by a ViewModel exposing flow-based state. This creates a predictable loop for reliable UI updates.
To recover UI state after process death, integrate SavedStateHandle within your MVI ViewModel to serialize and restore the State. This ensures the single source of UI data survives system-initiated process termination reliably.
Yes, this MVI approach standardizes Android/KMP screen logic by enforcing flow-based State, Action, and Event handling. It relies on Kotlin Flow state exposure via StateFlow, making it compatible with KMP architectures.
Navigation and snackbar side effects trigger multiple times when state is observed without lifecycle-aware collection. Using Channel.BUFFERED for event emission and ObserveAsEvents for consumption ensures one-time events are delivered exactly once.
To map domain errors to UI text, transform them into UiText objects within your MVI ViewModel before updating the State. This production-friendly approach separates presentation formatting from domain logic for reliable UI rendering.
nksethImplement idiomatic Kotlin patterns with coroutines, Flow, and multiplatform architecture.
maichanchinhImplement MVI architecture for Android Activities with Jetpack Compose.
xxihManage shared Compose UI patterns across Kotlin Multiplatform projects.
kvithayathilStandardize MVI presentation layers in Android and Kotlin Multiplatform apps.
