android-viewmodel

Use StateFlow in an Android ViewModel to manage persistent UI states like loading, success, and error with proper initialization and thread-safe updates. This ensures robust UI state exposure that survives configuration changes.

Navigation events re-trigger because they are likely exposed as StateFlow. Expose transient UI events like navigation or toasts as SharedFlow instead, which handles one-off events correctly without re-emitting them during configuration changes.

Collect ViewModel StateFlow in Jetpack Compose using lifecycle-aware collection methods. This ensures the UI layer only consumes state when actively visible, optimizing performance and preventing unnecessary updates.

Use SharedFlow for one-off events in Android. SharedFlow is designed for transient UI events like toasts and navigation, whereas StateFlow is meant for persistent UI state, ensuring events are not redundantly re-triggered.

Adhere to ViewModel lifecycle management and coroutine scoping best practices to manage Android ViewModel lifecycle with coroutines, clearing coroutines automatically when the ViewModel is cleared.

Yes, the Android ViewModel pattern works with traditional View-based UIs. It demonstrates how to collect state and events across different Android UI toolkits using lifecycle-aware collection methods.