State in ViewModel in Android Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of ViewModel in Android development?

ViewModel holds and manages UI-related data in a lifecycle-conscious way. It survives configuration changes like screen rotations, keeping the UI state intact.

beginner

How does MutableLiveData help in managing state inside a ViewModel?

MutableLiveData allows the ViewModel to hold data that can be observed by the UI. When data changes, the UI updates automatically.

intermediate

Why should UI state be stored in ViewModel instead of Activity or Fragment?

Storing UI state in ViewModel prevents data loss during configuration changes and separates UI logic from UI controllers, making code cleaner and more testable.

advanced

What is the difference between LiveData and StateFlow in ViewModel state management?

LiveData is lifecycle-aware and designed for UI observation. StateFlow is a Kotlin Flow that holds state and supports coroutines, offering more flexibility and modern reactive patterns.

intermediate

How do you update state inside a ViewModel using MutableStateFlow?

You update the state by assigning a new value to the MutableStateFlow variable, for example: _state.value = newValue. Observers get notified automatically.

What happens to ViewModel data when the device rotates?

A Data is preserved and reused

B Data is lost and reset

C ViewModel is destroyed and recreated

D UI crashes

ViewModel survives configuration changes like rotation, so data is preserved and reused.

Which class is commonly used inside ViewModel to hold observable UI state?

A Bundle

B Intent

C MutableLiveData

D View

MutableLiveData holds observable data that UI components can watch for changes.

Which of these is a benefit of using StateFlow over LiveData?

A Supports coroutines and reactive streams

B Not lifecycle-aware

C Works only with Java

D Cannot hold state

StateFlow supports Kotlin coroutines and reactive programming, offering more flexibility.

Where should you NOT store UI state in Android apps?

A ViewModelStore

B ViewModel

C Fragment

D Activity

Storing UI state in Activity risks losing data on configuration changes.

How do UI components get notified of state changes in ViewModel?

A By polling the ViewModel

B Through observers on LiveData or StateFlow

C By restarting the Activity

D By manual refresh

UI components observe LiveData or StateFlow to get automatic updates when state changes.

Explain how ViewModel helps manage UI state during device rotation.

Think about what happens when the screen rotates and how ViewModel keeps data safe.

Describe the difference between LiveData and StateFlow for state management in ViewModel.

Consider their usage and features in Kotlin and Android.