Why ViewModel survives configuration changes in Android Kotlin - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a ViewModel instance in an Activity.

Android Kotlin

val viewModel = ViewModelProvider(this).get([1]::class.java)

Drag options to blanks, or click blank then click option'

AApplication

BMainActivity

CViewModelProvider

DMyViewModel

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the Activity class instead of the ViewModel class.

You need to pass your ViewModel class to get() to create or retrieve it.

2fill in blank

medium

Complete the code to extend the ViewModel class correctly.

Android Kotlin

class MyViewModel : [1]() {
  // ViewModel logic here
}

Drag options to blanks, or click blank then click option'

AActivity

BFragment

CViewModel

DApplication

Attempts:

3 left

💡 Hint

Common Mistakes

Extending Activity or Fragment instead of ViewModel.

Your ViewModel class must extend ViewModel to survive configuration changes.

3fill in blank

hard

Fix the error in the code to get the ViewModel in a Fragment.

Android Kotlin

val viewModel = ViewModelProvider([1]).get(MyViewModel::class.java)

Drag options to blanks, or click blank then click option'

ArequireActivity()

Bthis

Capplication

DviewLifecycleOwner

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'this' which refers to Fragment, creating a Fragment-scoped ViewModel.

Using requireActivity() shares the ViewModel between Fragment and its Activity, surviving configuration changes.

4fill in blank

hard

Fill both blanks to explain why ViewModel survives configuration changes.

Android Kotlin

ViewModel is stored in the [1] and tied to the [2] lifecycle.

Drag options to blanks, or click blank then click option'

AViewModelStore

BActivity

CApplication

DFragment

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing Application with ViewModelStore or Fragment.

The ViewModelStore keeps ViewModels alive, and they are tied to the Activity lifecycle, which survives configuration changes.

5fill in blank

hard

Fill all three blanks to complete the explanation of ViewModel behavior.

Android Kotlin

When configuration changes, the [1] is destroyed but the [2] and [3] remain, keeping ViewModel alive.

Drag options to blanks, or click blank then click option'

AActivity

BViewModelStore

CFragment

DApplication

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking Activity survives configuration changes.

The Activity is destroyed and recreated on configuration change, but the Application and ViewModelStore survive, so ViewModel data is preserved.

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