What problem does Jetpack ViewModel solve during configuration changes?

What's really being asked

This question tests your understanding of a fundamental problem in Android development: state management across configuration changes. The interviewer wants to see that you don't just know what a ViewModel is, but why it exists. It's a proxy for understanding the Activity/Fragment lifecycle, memory management, and the separation of concerns between UI controllers and data models.

The full answer

A strong answer has three parts. First, define the problem: configuration changes like screen rotation cause the system to destroy and recreate the current Activity or Fragment. This means any non-persistent data held in memory by that component is lost. Second, explain the solution: a ViewModel is a lifecycle-aware component designed to survive these specific configuration changes. When the Activity is recreated, it receives the same ViewModel instance that existed before the change, preserving its data. Third, clarify its scope: the ViewModel is finally cleared and its onCleared() method is called only when the associated Activity is finished or the Fragment is permanently detached, not just during recreation.

The mistakes people make

A major red flag is confusing the role of ViewModel with onSaveInstanceState. ViewModel is for surviving configuration changes and holding complex UI data in memory. onSaveInstanceState is for surviving system-initiated process death and only handles small amounts of serializable data. Another mistake is saying a ViewModel never gets destroyed; it's tied to the UI controller's lifecycle scope. Finally, suggesting that a ViewModel can hold a direct reference to an Activity or View is a serious red flag, as this creates a memory leak.

What usually comes next

"When would you use onSaveInstanceState instead of a ViewModel?" (Answer: For process death, and for small, simple, serializable data). "How does a ViewModel actually survive? Where is it stored?" (Answer: It's held by a ViewModelStore which is managed by the Activity/Fragment and retained by the system across configuration changes). "What is the onCleared() method used for?" (Answer: Releasing resources, like cancelling coroutines or cleaning up data stream subscriptions, when the ViewModel is about to be destroyed).

A concrete example

Imagine a user has typed "San Francisco" into a search box in a weather app but hasn't hit search yet. If they rotate their phone, the Activity is destroyed and recreated. Without a ViewModel, the text "San Francisco" would disappear. By storing this string in a MutableStateFlow or LiveData within a ViewModel, the new Activity instance can observe this data and immediately repopulate the search box, providing a seamless user experience.