Dispatchers.Main, IO, Default behavior in Kotlin - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to launch a coroutine on the main thread.

Kotlin

CoroutineScope(Dispatchers.[1]).launch {
    // UI update code here
}

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

AMain

BDefault

CUnconfined

DIO

Attempts:

3 left

💡 Hint

Common Mistakes

Using Dispatchers.IO for UI updates causes errors because it's for background work.

Using Dispatchers.Default does not guarantee running on the main thread.

Dispatchers.Main is used to run coroutines on the main thread, which is necessary for UI updates.

2fill in blank

medium

Complete the code to perform a network request on the appropriate dispatcher.

Kotlin

CoroutineScope(Dispatchers.[1]).launch {
    val data = fetchData()
    // process data
}

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

AIO

BMain

CDefault

DUnconfined

Attempts:

3 left

💡 Hint

Common Mistakes

Using Dispatchers.Main for network calls can freeze the UI.

Dispatchers.Default is for CPU-intensive tasks, not IO.

Dispatchers.IO is optimized for blocking IO tasks like network or disk operations.

3fill in blank

hard

Fix the error in the code to run a CPU-intensive task on the correct dispatcher.

Kotlin

CoroutineScope(Dispatchers.[1]).launch {
    val result = heavyComputation()
    // use result
}

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

AMain

BDefault

CIO

DUnconfined

Attempts:

3 left

💡 Hint

Common Mistakes

Using Dispatchers.IO for CPU tasks can cause thread starvation.

Using Dispatchers.Main for heavy work blocks the UI.

Dispatchers.Default is optimized for CPU-intensive tasks like heavy computations.

4fill in blank

hard

Fill both blanks to create a coroutine that switches from IO to Main dispatcher.

Kotlin

CoroutineScope(Dispatchers.[1]).launch {
    val data = fetchData()
    withContext(Dispatchers.[2]) {
        updateUI(data)
    }
}

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

AIO

BMain

CDefault

DUnconfined

Attempts:

3 left

💡 Hint

Common Mistakes

Not switching back to Main dispatcher before UI update.

Using Default dispatcher for IO tasks.

Start on Dispatchers.IO for background work, then switch to Dispatchers.Main to update UI.

5fill in blank

hard

Fill all three blanks to create a coroutine that performs CPU work, then IO, then updates UI.

Kotlin

CoroutineScope(Dispatchers.[1]).launch {
    val cpuResult = heavyComputation()
    val ioResult = withContext(Dispatchers.[2]) {
        fetchData()
    }
    withContext(Dispatchers.[3]) {
        updateUI(cpuResult, ioResult)
    }
}

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

ADefault

BIO

CMain

DUnconfined

Attempts:

3 left

💡 Hint

Common Mistakes

Using Main dispatcher for CPU or IO tasks.

Not switching dispatchers properly causing UI freezes.

Use Default for CPU work, switch to IO for network, then Main for UI updates.

Practice

1. Which Dispatcher should you use in Kotlin when updating the user interface (UI)?

easy

A. Dispatchers.Main

B. Dispatchers.IO

C. Dispatchers.Default

D. Dispatchers.Unconfined

Solution

1. Step 1: Understand UI thread requirements

   UI updates must happen on the main thread to avoid crashes or freezes.

2. Step 2: Match Dispatcher to UI work

   Dispatchers.Main is designed for UI tasks on the main thread.

3. Final Answer:

   Dispatchers.Main -> Option A

4. Quick Check:

   UI work = Dispatchers.Main [OK]

Hint: UI updates always use Dispatchers.Main [OK]

Common Mistakes:

• Using Dispatchers.IO for UI updates
• Using Dispatchers.Default for UI work
• Confusing Dispatchers.Unconfined with Main

2. Which of the following is the correct way to launch a coroutine on the IO dispatcher in Kotlin?

easy

A. CoroutineScope.launch(Dispatchers.IO) { /* IO work */ }

B. CoroutineScope(Dispatchers.Main).launch { /* IO work */ }

C. CoroutineScope(Dispatchers.Default).launch { /* IO work */ }

D. CoroutineScope(Dispatchers.IO).launch { /* IO work */ }

Solution

1. Step 1: Identify correct CoroutineScope usage

   To launch a coroutine on a specific dispatcher, create CoroutineScope with that dispatcher.

2. Step 2: Check syntax correctness

   CoroutineScope(Dispatchers.IO).launch { ... } is correct syntax for IO dispatcher.

3. Final Answer:

   CoroutineScope(Dispatchers.IO).launch { /* IO work */ } -> Option D

4. Quick Check:

   IO dispatcher launch = CoroutineScope(Dispatchers.IO).launch { /* IO work */ } [OK]

Hint: Use CoroutineScope(Dispatchers.IO).launch for IO tasks [OK]

Common Mistakes:

• Using Dispatchers.Main for IO tasks
• Incorrect CoroutineScope.launch syntax
• Using Dispatchers.Default for IO tasks

3. What will be the output of the following Kotlin code snippet?

import kotlinx.coroutines.*

fun main() = runBlocking {
    launch(Dispatchers.Default) {
        println("Running on: " + Thread.currentThread().name)
    }.join()
}

medium

A. Running on: DefaultDispatcher-worker-1

B. Running on: main

C. Running on: IO-thread-1

D. Running on: Unconfined

Solution

1. Step 1: Identify the dispatcher used

   The coroutine is launched with Dispatchers.Default, which uses a shared background thread pool.

2. Step 2: Understand thread naming

   Threads in Default dispatcher are named like "DefaultDispatcher-worker-1".

3. Final Answer:

   Running on: DefaultDispatcher-worker-1 -> Option A

4. Quick Check:

   Dispatchers.Default runs on DefaultDispatcher-worker threads [OK]

Hint: Default dispatcher uses background worker threads [OK]

Common Mistakes:

• Assuming it runs on main thread
• Confusing IO thread names with Default
• Expecting Unconfined dispatcher output

4. Consider this Kotlin coroutine code snippet:

CoroutineScope(Dispatchers.Main).launch {
    withContext(Dispatchers.IO) {
        // Perform file read
    }
    println("File read complete")
}

What is the main issue if this code is run in an Android app?

medium

A. Using Dispatchers.Main inside withContext causes a crash

B. File read should be done on Dispatchers.Default, not IO

C. No issue; this is the correct way to switch dispatchers

D. println runs on IO dispatcher causing UI freeze

Solution

1. Step 1: Analyze dispatcher switching

   The code launches on Main dispatcher, then switches to IO for file reading.

2. Step 2: Confirm correct usage

   Switching to Dispatchers.IO for file I/O and back to Main for UI is correct practice.

3. Final Answer:

   No issue; this is the correct way to switch dispatchers -> Option C

4. Quick Check:

   Dispatcher switching Main ↔ IO is correct [OK]

Hint: Switch to IO for I/O, back to Main for UI [OK]

Common Mistakes:

• Thinking Dispatchers.Default is for I/O
• Believing println runs on IO dispatcher
• Assuming dispatcher switch causes crash

5. You want to perform a CPU-intensive calculation without blocking the UI in a Kotlin Android app. Which dispatcher should you use and why?

Select the best option.

hard

A. Dispatchers.Main, because it runs on the main thread

B. Dispatchers.Default, because it is optimized for CPU-heavy work

C. Dispatchers.Unconfined, because it runs immediately

D. Dispatchers.IO, because it handles background tasks

Solution

1. Step 1: Identify task type

   CPU-intensive tasks need background threads to avoid freezing UI.

2. Step 2: Match dispatcher to CPU work

   Dispatchers.Default is designed for CPU-heavy tasks using a shared thread pool.

3. Final Answer:

   Dispatchers.Default, because it is optimized for CPU-heavy work -> Option B

4. Quick Check:

   CPU tasks = Dispatchers.Default [OK]

Hint: Use Default dispatcher for CPU-heavy tasks [OK]

Common Mistakes:

• Using Main dispatcher for CPU work
• Confusing IO dispatcher with CPU dispatcher
• Using Unconfined dispatcher for heavy tasks