StateFlow for reactive state in Android Kotlin - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a MutableStateFlow with initial value 0.

Android Kotlin

val counter = MutableStateFlow([1])

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

Afalse

B"0"

Cnull

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string "0" instead of integer 0

Leaving the initial value null

Using a boolean false instead of a number

The MutableStateFlow must be initialized with a starting value. Here, 0 is the correct integer initial value.

2fill in blank

medium

Complete the code to expose the StateFlow as a read-only flow from MutableStateFlow.

Android Kotlin

val _counter = MutableStateFlow(0)
val counter: StateFlow<Int> = _counter.[1]

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

AtoFlow()

BtoStateFlow()

CasStateFlow()

Dstate()

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-existent function like toStateFlow()

Trying to assign MutableStateFlow directly without conversion

Using toFlow() which returns a Flow, not StateFlow

Use asStateFlow() to expose a read-only StateFlow from a MutableStateFlow.

3fill in blank

hard

Fix the error in updating the MutableStateFlow value inside a function.

Android Kotlin

fun increment() {
  _counter.[1] = _counter.value + 1
}

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

Avalue

BsetValue

Cemit

Dupdate

Attempts:

3 left

💡 Hint

Common Mistakes

Using emit which is a suspend function and not available on MutableStateFlow

Trying to call setValue which does not exist

Using update which is an extension function but not a property

To update the value of a MutableStateFlow, assign the new value to its value property.

4fill in blank

hard

Fill both blanks to collect the StateFlow in a lifecycle-aware way inside a Fragment.

Android Kotlin

viewLifecycleOwner.lifecycleScope.launchWhenStarted {
  counter.[1] { value ->
    textView.text = value.toString()
  }
}

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

Acollect

BcollectLatest

Claunch

Dobserve

Attempts:

3 left

💡 Hint

Common Mistakes

Using collectLatest which cancels previous collector but not necessary here

Using launch which is for starting coroutines, not collecting flows

Using observe which is for LiveData, not StateFlow

Use collect to observe StateFlow emissions inside a coroutine.

5fill in blank

hard

Fill both blanks to create a StateFlow that holds a list of strings and add a new item.

Android Kotlin

private val _items = MutableStateFlow<List<String>>([1])
val items: StateFlow<List<String>> = _items.asStateFlow()

fun addItem(newItem: String) {
  _items.value = _items.value [2] listOf(newItem)
}

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

AemptyList()

B+

Cplus

DlistOf()

Attempts:

3 left

💡 Hint

Common Mistakes

Initializing with listOf() without elements

Using + operator which works but plus() is clearer for lists

Trying to modify the list directly instead of creating a new list

Initialize with an empty list using emptyList(). Use plus to add an item to the list immutably.

Practice

1. What is the main purpose of StateFlow in Android Kotlin development?

easy

A. To hold and emit state updates reactively to observers

B. To perform background network requests

C. To store user preferences permanently

D. To manage database transactions

Solution

1. Step 1: Understand StateFlow's role

   StateFlow is designed to hold a state value and emit updates whenever the state changes.

2. Step 2: Compare with other options

   Options A, B, and D describe unrelated tasks like storage, networking, or database management, which are not StateFlow's purpose.

3. Final Answer:

   To hold and emit state updates reactively to observers -> Option A

4. Quick Check:

   StateFlow = reactive state holder [OK]

Hint: StateFlow always relates to reactive state updates [OK]

Common Mistakes:

• Confusing StateFlow with networking or storage APIs
• Thinking StateFlow stores data permanently
• Assuming StateFlow manages database directly

2. Which of the following is the correct way to declare a mutable StateFlow holding an integer value starting at 0?

easy

A. val state = StateFlow<Int>(0)

B. val state = MutableStateFlow(0)

C. val state = mutableStateFlowOf(0)

D. val state = StateFlow.mutable(0)

Solution

1. Step 1: Recall MutableStateFlow syntax

   The correct way to create a mutable StateFlow is using MutableStateFlow(initialValue).

2. Step 2: Check each option

   val state = StateFlow<Int>(0) uses StateFlow constructor which is not allowed. val state = mutableStateFlowOf(0) uses a non-existent function. val state = StateFlow.mutable(0) uses invalid syntax.

3. Final Answer:

   val state = MutableStateFlow(0) -> Option B

4. Quick Check:

   MutableStateFlow = mutable state holder [OK]

Hint: MutableStateFlow constructor takes initial value directly [OK]

Common Mistakes:

• Trying to instantiate StateFlow directly
• Using wrong function names like mutableStateFlowOf
• Incorrect syntax for mutable StateFlow creation

3. Given the following code snippet, what will be printed to the console?

val state = MutableStateFlow(0)

state.value = 5
println(state.value)

medium

A. Compilation error

B. 0

C. null

D. 5

Solution

1. Step 1: Understand MutableStateFlow value assignment

   MutableStateFlow's value property can be updated directly, changing the current state.

2. Step 2: Trace the code execution

   Initially, state.value is 0. Then it is set to 5. Printing state.value outputs 5.

3. Final Answer:

   5 -> Option D

4. Quick Check:

   state.value after assignment = 5 [OK]

Hint: MutableStateFlow.value updates immediately and can be read directly [OK]

Common Mistakes:

• Assuming initial value remains unchanged
• Thinking value is nullable and prints null
• Expecting compilation error due to direct assignment

4. Identify the error in the following Kotlin code using StateFlow:

val state = MutableStateFlow(0)

fun updateState(newValue: Int) {
  state.emit(newValue)
}

medium

A. Cannot call emit on MutableStateFlow

B. MutableStateFlow does not hold an initial value

C. emit is a suspend function and must be called from a coroutine

D. StateFlow cannot be updated after creation

Solution

1. Step 1: Check usage of emit on MutableStateFlow

   The emit function is a suspend function and requires a coroutine context to be called.

2. Step 2: Analyze the code context

   The function updateState is not marked suspend and does not launch a coroutine, so calling emit here causes an error.

3. Final Answer:

   emit is a suspend function and must be called from a coroutine -> Option C

4. Quick Check:

   emit requires coroutine context [OK]

Hint: emit is suspend; call only inside coroutine or suspend function [OK]

Common Mistakes:

• Calling emit outside coroutine without suspend
• Confusing emit with direct value assignment
• Assuming MutableStateFlow has no initial value

5. You want to expose a read-only StateFlow from a ViewModel while keeping the ability to update the state internally. Which of the following is the best practice to achieve this?

hard

A. Keep a private MutableStateFlow and expose a public StateFlow using asStateFlow()

B. Expose the MutableStateFlow as a public property and update it internally

C. Declare a public MutableStateFlow and update it directly from outside the ViewModel

D. Use a regular Flow instead of StateFlow for state updates

Solution

1. Step 1: Understand encapsulation of state

   To prevent external modification, keep MutableStateFlow private inside ViewModel.

2. Step 2: Expose read-only StateFlow

   Use asStateFlow() to expose a read-only StateFlow to observers outside the ViewModel.

3. Step 3: Evaluate other options

   Declare a public MutableStateFlow and update it directly from outside the ViewModel breaks encapsulation. Expose the MutableStateFlow as a public property and update it internally exposes mutable state publicly. Use a regular Flow instead of StateFlow for state updates changes the reactive type unnecessarily.

4. Final Answer:

   Keep a private MutableStateFlow and expose a public StateFlow using asStateFlow() -> Option A

5. Quick Check:

   Private MutableStateFlow + public asStateFlow() = best practice [OK]

Hint: Use private MutableStateFlow + public asStateFlow() for safe exposure [OK]

Common Mistakes:

• Making MutableStateFlow public and mutable externally
• Not using asStateFlow() to expose read-only state
• Replacing StateFlow with Flow unnecessarily