Why coroutines simplify async programming in Android Kotlin - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to launch a coroutine in the main scope.

Android Kotlin

GlobalScope.[1] {
  println("Hello from coroutine")
}

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

Aasync

BrunBlocking

Cdelay

Dlaunch

Attempts:

3 left

💡 Hint

Common Mistakes

Using runBlocking blocks the thread, which is not desired here.

Using delay is a suspending function, not a coroutine builder.

The launch function starts a new coroutine without blocking the current thread.

2fill in blank

medium

Complete the code to suspend a coroutine for 1 second.

Android Kotlin

suspend fun waitOneSecond() {
  [1](1000L)
}

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

Await

BThread.sleep

Cdelay

Dsleep

Attempts:

3 left

💡 Hint

Common Mistakes

Using Thread.sleep blocks the thread, which defeats the purpose of coroutines.

The delay function suspends the coroutine without blocking the thread.

3fill in blank

hard

Fix the error in the coroutine builder to return a deferred result.

Android Kotlin

val deferred = GlobalScope.[1] {
  42
}

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

Aasync

Bdelay

CrunBlocking

Dlaunch

Attempts:

3 left

💡 Hint

Common Mistakes

Using launch returns Job, not a result.

Using delay is not a builder.

The async builder returns a Deferred, which can hold a result.

4fill in blank

hard

Fill both blanks to create a coroutine scope and launch a coroutine.

Android Kotlin

val scope = CoroutineScope([1] + Job())
scope.[2] {
  println("Running in scope")
}

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

ADispatchers.Main

Blaunch

CDispatchers.IO

Dasync

Attempts:

3 left

💡 Hint

Common Mistakes

Using async when no result is needed.

Using Dispatchers.IO for UI work.

Use Dispatchers.Main for UI thread and launch to start coroutine.

5fill in blank

hard

Fill the two blanks to create a suspending function that fetches data asynchronously.

Android Kotlin

suspend fun fetchData(): String {
  return withContext([1]) {
    val data = apiCall()
    if (data.isNotEmpty()) data else [2]
  }
}

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

ADispatchers.IO

Breturn

C"No data"

Dprintln

Attempts:

3 left

💡 Hint

Common Mistakes

Using Dispatchers.Main for network calls.

Using println instead of returning data.

withContext(Dispatchers.IO) switches to IO thread for network call.
The if expression returns the data or "No data" if empty.

Practice

1. Why do coroutines simplify asynchronous programming in Kotlin?

easy

A. They allow writing async code that looks like normal sequential code.

B. They force all code to run on the main thread.

C. They require complex callback interfaces.

D. They block the UI until tasks finish.

Solution

1. Step 1: Understand coroutine purpose

   Coroutines let you write asynchronous code that looks like normal sequential code, making it easier to read and maintain.

2. Step 2: Compare with other async methods

   Unlike callbacks or threads, coroutines avoid blocking the main thread and complex callback nesting.

3. Final Answer:

   They allow writing async code that looks like normal sequential code. -> Option A

4. Quick Check:

   Async code looks sequential = D [OK]

Hint: Coroutines make async code look like normal code [OK]

Common Mistakes:

• Thinking coroutines block the UI thread
• Confusing coroutines with callbacks
• Believing coroutines require complex interfaces

2. Which of the following is the correct way to start a coroutine in Kotlin?

easy

A. launch { doWork() }

B. startCoroutine(doWork())

C. runBlocking { doWork() }

D. async doWork()

Solution

1. Step 1: Identify coroutine builders

   The launch builder is used to start a new coroutine without blocking the current thread.

2. Step 2: Check syntax correctness

   launch { doWork() } uses correct syntax: launch { doWork() }. Options A and D are invalid syntax, and C blocks the thread.

3. Final Answer:

   launch { doWork() } -> Option A

4. Quick Check:

   Use launch to start coroutine [OK]

Hint: Use launch { } to start coroutines easily [OK]

Common Mistakes:

• Using runBlocking for UI code
• Writing async without parentheses
• Trying to call startCoroutine directly

3. What will be the output of this Kotlin coroutine code?

fun main() = runBlocking {
  launch {
    delay(100L)
    println("World")
  }
  println("Hello")
}

medium

A. World\nHello

B. Hello\nWorld

C. Hello

D. World

Solution

1. Step 1: Analyze runBlocking and launch

   runBlocking blocks the main thread until all coroutines inside complete. The launch coroutine starts and delays 100ms before printing "World".

2. Step 2: Trace print order

   The main coroutine prints "Hello" immediately, then after 100ms the launched coroutine prints "World".

3. Final Answer:

   Hello\nWorld -> Option B

4. Quick Check:

   runBlocking waits, launch delays, so Hello then World [OK]

Hint: runBlocking waits; launch runs concurrently [OK]

Common Mistakes:

• Assuming launch blocks immediately
• Ignoring delay effect
• Thinking output is reversed

4. Identify the error in this coroutine code snippet:

fun fetchData() {
  GlobalScope.launch {
    val data = fetchFromNetwork()
  }
  println(data)
}

medium

A. println cannot print variables.

B. GlobalScope.launch cannot be used inside functions.

C. fetchFromNetwork() must not be called inside launch.

D. data is accessed outside coroutine scope causing an error.

Solution

1. Step 1: Check variable scope

   The variable data is declared inside the coroutine but accessed outside it, causing a compile error.

2. Step 2: Understand coroutine execution

   The coroutine runs asynchronously, so println(data) runs before data is assigned, and data is not visible outside.

3. Final Answer:

   data is accessed outside coroutine scope causing an error. -> Option D

4. Quick Check:

   Variable scope error = A [OK]

Hint: Variables inside coroutine not visible outside [OK]

Common Mistakes:

• Thinking GlobalScope.launch is invalid here
• Assuming fetchFromNetwork can't be called inside launch
• Believing println can't print variables

5. You want to fetch user data and then update the UI without blocking the main thread. Which coroutine approach is best?

hard

A. Use nested callbacks inside GlobalScope.launch to fetch and update UI.

B. Use runBlocking on the main thread to fetch data synchronously.

C. Launch a coroutine with Dispatchers.IO to fetch data, then switch to Dispatchers.Main to update UI.

D. Fetch data on main thread and update UI immediately.

Solution

1. Step 1: Identify threading needs

   Fetching data should happen off the main thread to avoid freezing UI, so Dispatchers.IO is suitable.

2. Step 2: Update UI on main thread

   UI updates must happen on Dispatchers.Main to avoid errors and keep UI responsive.

3. Step 3: Combine with coroutine context switching

   Switching context inside coroutine allows smooth async fetch and UI update without blocking.

4. Final Answer:

   Launch a coroutine with Dispatchers.IO to fetch data, then switch to Dispatchers.Main to update UI. -> Option C

5. Quick Check:

   IO for work, Main for UI = A [OK]

Hint: Use IO dispatcher for work, Main for UI updates [OK]

Common Mistakes:

• Blocking main thread with runBlocking
• Updating UI off main thread
• Using nested callbacks instead of coroutines