Side effects (LaunchedEffect, SideEffect) in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What happens when LaunchedEffect key changes?

Consider this Compose snippet:

var count by remember { mutableStateOf(0) }
LaunchedEffect(count) {
  println("Count is $count")
}

What happens when count changes?

Android Kotlin

var count by remember { mutableStateOf(0) }
LaunchedEffect(count) {
  println("Count is $count")
}

A The block runs only once when the composable is first composed.

B The block inside LaunchedEffect restarts and prints the new count value.

C The block never runs because count is mutable.

D The block runs repeatedly in an infinite loop.

💡 Hint

LaunchedEffect runs its block when the key changes.

LaunchedEffect watches the key parameter. When count changes, it cancels the previous coroutine and launches a new one, printing the updated value.

❓ lifecycle

intermediate

When does SideEffect run in Compose?

Given this Compose code:

SideEffect {
  println("SideEffect executed")
}

When is this block executed?

Android Kotlin

SideEffect {
  println("SideEffect executed")
}

A After every successful recomposition of the composable.

B Only once when the composable is first composed.

C Before the composable is composed.

D Only when the composable is disposed.

💡 Hint

Think about when SideEffect is designed to run in the Compose lifecycle.

SideEffect runs after every recomposition, allowing side effects that need to happen after UI updates.

🔧 Debug

advanced

Why does this LaunchedEffect cause repeated prints?

Look at this code:

var text by remember { mutableStateOf("") }
LaunchedEffect(Unit) {
  while(true) {
    delay(1000)
    println("Tick")
  }
}
Button(onClick = { text += "a" }) {
  Text(text)
}

What is the problem with this LaunchedEffect?

Android Kotlin

var text by remember { mutableStateOf("") }
LaunchedEffect(Unit) {
  while(true) {
    delay(1000)
    println("Tick")
  }
}
Button(onClick = { text += "a" }) {
  Text(text)
}

A The LaunchedEffect never runs because Unit is not a valid key.

B The LaunchedEffect restarts on every recomposition causing multiple "Tick" prints per second.

C The LaunchedEffect runs only once and prints "Tick" every second as expected.

D The Button click causes the LaunchedEffect to cancel immediately.

💡 Hint

Consider what key Unit means for LaunchedEffect.

Using Unit as key means LaunchedEffect runs once when first composed and does not restart on recompositions, so it prints "Tick" every second as intended.

🧠 Conceptual

advanced

Difference between LaunchedEffect and SideEffect?

Which statement correctly describes the difference between LaunchedEffect and SideEffect in Jetpack Compose?

A LaunchedEffect runs suspend functions and can launch coroutines; SideEffect runs synchronously after recomposition.

B LaunchedEffect runs only once; SideEffect runs only on disposal.

C Both run suspend functions but LaunchedEffect cancels on key change; SideEffect does not.

D SideEffect launches coroutines; LaunchedEffect runs synchronously after recomposition.

💡 Hint

Think about coroutine support and timing of execution.

LaunchedEffect is designed to launch coroutines and supports suspend functions. SideEffect runs synchronously after every recomposition and cannot run suspend functions.

📝 Syntax

expert

What error occurs with this LaunchedEffect usage?

Analyze this code snippet:

LaunchedEffect {
  println("Hello")
}

What error will this cause?

Android Kotlin

LaunchedEffect {
  println("Hello")
}

A Type error: LaunchedEffect expects a suspend lambda.

B Runtime error: LaunchedEffect block cannot print to console.

C Syntax error: Missing key parameter in LaunchedEffect call.

D No error: This code runs fine and prints "Hello" once.

💡 Hint

LaunchedEffect(vararg keys: Any?, block: suspend CoroutineScope.() -> Unit); vararg keys can be omitted.

No syntax error: keys is vararg Any? and can be empty/omitted. The block runs once when the composable enters the composition, similar to LaunchedEffect(Unit).

Practice

1. What is the main purpose of LaunchedEffect in Jetpack Compose?

easy

A. To run suspend functions when a key changes

B. To immediately update UI elements

C. To create a new composable function

D. To handle user input events

Solution

1. Step 1: Understand LaunchedEffect role

   LaunchedEffect is designed to run suspend functions in response to changes in keys.

2. Step 2: Differentiate from UI updates

   It does not directly update UI or handle input but manages side effects like network calls.

3. Final Answer:

   To run suspend functions when a key changes -> Option A

4. Quick Check:

   LaunchedEffect runs suspend code on key change = D [OK]

Hint: LaunchedEffect runs suspend code on key changes [OK]

Common Mistakes:

• Confusing LaunchedEffect with UI rendering
• Thinking it handles user input directly
• Assuming it runs only once without key

2. Which of the following is the correct syntax to use SideEffect in a composable?

easy

A. SideEffect.launch { /* suspend code */ }

B. SideEffect { /* code to run after every recomposition */ }

C. SideEffect() { /* code to run once */ }

D. SideEffect.runOnUiThread { /* UI update code */ }

Solution

1. Step 1: Recall SideEffect usage

   SideEffect is a composable function that takes a lambda to run after every successful recomposition.

2. Step 2: Check syntax correctness

   SideEffect { /* code to run after every recomposition */ } matches the correct syntax without parentheses or suspend keywords.

3. Final Answer:

   SideEffect { /* code to run after every recomposition */ } -> Option B

4. Quick Check:

   SideEffect uses lambda syntax without parentheses = C [OK]

Hint: SideEffect uses simple lambda syntax without parentheses [OK]

Common Mistakes:

• Adding parentheses after SideEffect
• Trying to launch suspend code inside SideEffect
• Using SideEffect as a coroutine builder

3. What will be the output behavior of this code snippet?

var count = 0
LaunchedEffect(Unit) {
  count += 1
}
SideEffect {
  println("Count: $count")
}

medium

A. Prints "Count: 0" repeatedly on every recomposition

B. Prints "Count: 1" repeatedly on every recomposition

C. Prints "Count: 1" once after first composition

D. Prints "Count: 0" once and never again

Solution

1. Step 1: Analyze LaunchedEffect behavior

   LaunchedEffect(Unit) runs once on first composition and increments count to 1.

2. Step 2: Analyze SideEffect behavior

   SideEffect runs after every recomposition and prints current count value. However, since count is a regular variable and not a state, recompositions do not trigger updates to count or cause recompositions to reflect the incremented value. The printed value remains 0 repeatedly.

3. Final Answer:

   Prints "Count: 0" repeatedly on every recomposition -> Option A

4. Quick Check:

   Regular variable not triggering recomposition; SideEffect prints initial value repeatedly = B [OK]

Hint: Regular variables don't trigger recomposition; SideEffect prints initial value repeatedly [OK]

Common Mistakes:

• Assuming SideEffect runs only once
• Thinking count increments on every recomposition
• Confusing LaunchedEffect and SideEffect timing

4. Identify the error in this code using LaunchedEffect:

@Composable
fun MyScreen() {
  LaunchedEffect {
    delay(1000)
    println("Hello")
  }
}

medium

A. Cannot call delay inside LaunchedEffect

B. LaunchedEffect must be called outside composable

C. println cannot be used inside composable

D. Missing key parameter in LaunchedEffect call

Solution

1. Step 1: Check LaunchedEffect syntax

   LaunchedEffect requires at least one key parameter to track changes and restart the coroutine.

2. Step 2: Confirm other parts are valid

   Calling delay and println inside LaunchedEffect is allowed; it runs suspend code.

3. Final Answer:

   Missing key parameter in LaunchedEffect call -> Option D

4. Quick Check:

   LaunchedEffect needs key parameter = B [OK]

Hint: LaunchedEffect always needs a key parameter [OK]

Common Mistakes:

• Omitting key parameter in LaunchedEffect
• Thinking delay is disallowed inside LaunchedEffect
• Believing println can't be used in composables

5. You want to fetch data from the network only once when a screen appears and log a message after every UI update. Which combination correctly uses LaunchedEffect and SideEffect?

hard

A. Use LaunchedEffect without key for fetching and SideEffect(Unit) for logging

B. Use SideEffect(Unit) for fetching and LaunchedEffect { println("UI updated") } for logging

C. Use LaunchedEffect(Unit) for fetching and SideEffect { println("UI updated") } for logging

D. Use SideEffect with key for fetching and LaunchedEffect(Unit) for logging

Solution

1. Step 1: Identify correct usage for fetching once

   LaunchedEffect with Unit key runs once on first composition, ideal for fetching data.

2. Step 2: Identify correct usage for logging after UI updates

   SideEffect runs after every recomposition, perfect for logging UI updates.

3. Final Answer:

   Use LaunchedEffect(Unit) for fetching and SideEffect { println("UI updated") } for logging -> Option C

4. Quick Check:

   LaunchedEffect for one-time suspend; SideEffect for every UI update = A [OK]

Hint: LaunchedEffect for one-time tasks; SideEffect for every UI update [OK]

Common Mistakes:

• Using SideEffect for suspend fetching
• Omitting key in LaunchedEffect
• Confusing which runs once vs every recomposition