Why ViewModel survives configuration changes in Android Kotlin - Quick Recap

Recall & Review

beginner

What is a ViewModel in Android?

A ViewModel is a class designed to store and manage UI-related data in a lifecycle conscious way. It helps data survive configuration changes like screen rotations.

beginner

How does ViewModel survive configuration changes?

ViewModel objects are tied to the lifecycle of an activity or fragment but are retained when those components are recreated during configuration changes, so data is preserved.

intermediate

What role does ViewModelStore play in ViewModel survival?

ViewModelStore holds ViewModel instances and is retained by the system during configuration changes, allowing ViewModels to persist across activity or fragment recreation.

intermediate

Why is it better to use ViewModel instead of onSaveInstanceState for data persistence?

ViewModel can hold complex data and live longer during configuration changes without serialization, unlike onSaveInstanceState which only saves small amounts of serializable data.

beginner

What happens to a ViewModel when the activity is finished or destroyed permanently?

When the activity or fragment is finished and not recreated, the ViewModel is cleared and its resources are released to avoid memory leaks.

What allows a ViewModel to survive configuration changes?

A It is stored in ViewModelStore which is retained by the system

B It saves data to a file automatically

C It uses onSaveInstanceState internally

D It recreates data every time the activity restarts

ViewModelStore keeps ViewModels alive during configuration changes, so data is preserved.

When does the ViewModel get cleared?

A When the user presses the back button once

B When the activity is recreated due to rotation

C When the app goes to background

D When the activity is finished permanently

ViewModel is cleared only when the activity or fragment is finished and not recreated.

Which of these is NOT a benefit of using ViewModel?

A Survives configuration changes

B Automatically saves data to disk

C Manages UI-related data lifecycle

D Prevents memory leaks by clearing data

ViewModel does not save data to disk automatically; it holds data in memory.

What is a configuration change in Android?

A Screen rotation or language change

B Changing app theme

C Installing a new app

D Updating Android OS

Configuration changes include screen rotations or language changes that recreate activities.

Why is ViewModel preferred over onSaveInstanceState for large data?

A Because ViewModel saves data to a database

B Because onSaveInstanceState is deprecated

C Because onSaveInstanceState can only save small serializable data

D Because ViewModel runs on a background thread

onSaveInstanceState is limited to small serializable data; ViewModel can hold larger and complex data in memory.

Explain in your own words why ViewModel survives configuration changes in Android.

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

Describe the difference between ViewModel and onSaveInstanceState for handling data during configuration changes.

Consider how each method stores data and when it is restored.

Practice

1. Why does a ViewModel survive configuration changes like screen rotations in Android?

easy

A. Because it is tied to the lifecycle of the activity or fragment and not recreated on configuration changes

B. Because it saves data to a file on disk automatically

C. Because it uses static variables to hold data

D. Because it runs in a separate background thread

Solution

1. Step 1: Understand ViewModel lifecycle

   A ViewModel is designed to be tied to the lifecycle of an activity or fragment but survives configuration changes like rotations.

2. Step 2: Why it survives configuration changes

   When a configuration change happens, the activity is destroyed and recreated, but the ViewModel instance is retained and reused.

3. Final Answer:

   Because it is tied to the lifecycle of the activity or fragment and not recreated on configuration changes -> Option A

4. Quick Check:

   ViewModel lifecycle = survives config changes [OK]

Hint: ViewModel survives because it outlives activity recreation [OK]

Common Mistakes:

• Thinking ViewModel saves data to disk automatically
• Confusing ViewModel with static variables
• Assuming ViewModel runs on a background thread

2. Which of the following is the correct way to get a ViewModel instance in an Activity using Kotlin?

easy

A. val model = ViewModelProvider.get(this, MyViewModel::class.java)

B. val model = MyViewModel()

C. val model = ViewModelProvider(this).get(MyViewModel::class.java)

D. val model = ViewModel()

Solution

1. Step 1: Identify correct ViewModelProvider usage

   The correct syntax to get a ViewModel instance is using ViewModelProvider with the activity or fragment as owner.

2. Step 2: Check Kotlin syntax

   Using ViewModelProvider(this).get(MyViewModel::class.java) is the standard way to get the ViewModel instance.

3. Final Answer:

   val model = ViewModelProvider(this).get(MyViewModel::class.java) -> Option C

4. Quick Check:

   ViewModelProvider(this).get() = correct syntax [OK]

Hint: Use ViewModelProvider(this).get() to get ViewModel [OK]

Common Mistakes:

• Instantiating ViewModel directly with constructor
• Using incorrect ViewModelProvider syntax
• Confusing ViewModel class with instance

3. Given this code snippet in an Activity, what will be the output after a screen rotation?

class MyViewModel : ViewModel() {
  var counter = 0
}

// In Activity
val model = ViewModelProvider(this).get(MyViewModel::class.java)
model.counter += 1
println(model.counter)

medium

A. 1 on first launch, then resets to 0 after rotation

B. 1 on first launch, then increments to 2 after rotation

C. Always prints 0

D. Throws an error on rotation

Solution

1. Step 1: Understand ViewModel data retention

   The ViewModel instance survives configuration changes, so its data like counter is preserved.

2. Step 2: Trace counter increment

   On first launch, counter is 0, incremented to 1 and printed. After rotation, the same ViewModel instance is used, counter is 1, incremented to 2 and printed.

3. Final Answer:

   1 on first launch, then increments to 2 after rotation -> Option B

4. Quick Check:

   ViewModel retains data = increments preserved [OK]

Hint: ViewModel keeps data, so counter increments across rotations [OK]

Common Mistakes:

• Assuming ViewModel resets on rotation
• Thinking counter always starts at 0
• Expecting an error due to rotation

4. What is wrong with this code that tries to use ViewModel in an Activity?

class MyViewModel : ViewModel() {
  var data = "Hello"
}

// In Activity
val model = MyViewModel()
println(model.data)

medium

A. The println statement is incorrect

B. The data variable must be private

C. ViewModel cannot have variables

D. ViewModel should not be instantiated directly; use ViewModelProvider instead

Solution

1. Step 1: Identify ViewModel instantiation error

   ViewModel must be obtained via ViewModelProvider to survive configuration changes, not created with constructor.

2. Step 2: Explain consequence

   Direct instantiation means a new ViewModel is created every time, losing data on rotation.

3. Final Answer:

   ViewModel should not be instantiated directly; use ViewModelProvider instead -> Option D

4. Quick Check:

   Use ViewModelProvider, not constructor [OK]

Hint: Never instantiate ViewModel with constructor directly [OK]

Common Mistakes:

• Creating ViewModel with constructor
• Thinking private variables fix lifecycle issues
• Blaming println for errors

5. You want to keep user input data safe during screen rotations in your app. Which approach best uses ViewModel to achieve this?

hard

A. Store user input in a ViewModel property and update it on every input change

B. Save user input in SharedPreferences and reload after rotation

C. Use static variables in the Activity to hold user input

D. Recreate the ViewModel on each rotation and reset user input

Solution

1. Step 1: Identify best practice for preserving UI data

   ViewModel is designed to hold UI-related data that survives configuration changes like rotations.

2. Step 2: Choose correct data handling method

   Storing user input in a ViewModel property and updating it on input changes keeps data safe and avoids unnecessary disk operations.

3. Final Answer:

   Store user input in a ViewModel property and update it on every input change -> Option A

4. Quick Check:

   ViewModel holds UI data safely across rotations [OK]

Hint: Keep UI data in ViewModel properties updated live [OK]

Common Mistakes:

• Using SharedPreferences for temporary UI data
• Using static variables which can cause leaks
• Recreating ViewModel loses data