mvi-activity

To implement MVI architecture with Jetpack Compose, structure your Android Activity using sealed classes for actions and events, and leverage StateFlow and SharedFlow to manage UI state and side effects. This separates Activity, Screen, and ViewModel components for maintainable declarative UIs.

The best way to manage state in MVI is using StateFlow for immutable UI state and SharedFlow for one-time side effects like navigation or messages. This ensures predictable state changes and clear separation of concerns in Jetpack Compose.

You should use the MVI pattern when creating a new feature screen with complex user interactions and dynamic data display. It provides a robust template for predictable state management and enforces a clear separation between UI, state, actions, and events.

Yes, you can scaffold a new Android feature screen without manual boilerplate. This Skill generates the initial Activity, Screen, and ViewModel code following MVI best practices, establishing the StateFlow and SharedFlow setup for immediate development.

MVI architecture works exceptionally well with Jetpack Compose because it relies on immutable state objects. Compose UIs react directly to these state changes via StateFlow, creating a unidirectional data flow that naturally fits the declarative UI paradigm.

Using sealed classes for actions and events in Android MVI requires defining all possible state variations upfront, which can increase code verbosity for highly dynamic screens. However, it guarantees type safety and exhaustive state handling at compile time.