android-viewmodel

You can manage Android UI state by initializing a private MutableStateFlow with an initial value and exposing it as a public read-only StateFlow. For one-off events like navigation or toasts, use a MutableSharedFlow with replay set to 0.

The best way to handle transient events in an Android ViewModel is using SharedFlow with replay = 0. This ensures one-off events like snackbars or navigation commands are emitted thread-safely and delivered only once, preventing repeated emissions on configuration changes.

To ensure UI state survives configuration changes, store the state within an Android ViewModel using a MutableStateFlow. The ViewModel lifecycle outlives the UI recreation, and the StateFlow retains the current UI state value for the newly created Compose or View component to collect.

You can safely update StateFlow and emit SharedFlow events in an Android ViewModel by applying thread-safe update mechanisms. Use the update function for StateFlow to guarantee atomic state modifications and SharedFlow's emit function for thread-safe event delivery.

Yes, this Android ViewModel StateFlow pattern works with both Compose and Views. The Skill provides lifecycle-safe collection patterns for both UI paradigms, allowing you to collect the public StateFlow and SharedFlow without risking crashes or duplicate event handling.

You should use StateFlow for Android ViewModel UI state to gain explicit threading control and distinct lifecycle-safe collection patterns. StateFlow requires an initial value, ensuring the UI always has a default state to render, whereas SharedFlow handles one-off events without the sticky behavior of LiveData.