Dispatchers.Main, IO, Default behavior in Kotlin - Step-by-Step Execution

Concept Flow - Dispatchers.Main, IO, Default behavior

Start Coroutine

↓

Choose Dispatcher

↓

Main

↓

Run on UI

↓

Complete Coroutine

When a coroutine starts, it picks a dispatcher: Main for UI tasks, IO for input/output, Default for CPU work.

Execution Sample

Kotlin

launch(Dispatchers.Main) {
    println("Running on Main")
}
launch(Dispatchers.IO) {
    println("Running on IO")
}
launch(Dispatchers.Default) {
    println("Running on Default")
}

This code launches three coroutines, each running on a different dispatcher to handle UI, IO, and CPU tasks.

Execution Table

Step	Coroutine	Dispatcher	Thread Type	Action	Output
1	Coroutine 1	Dispatchers.Main	Main/UI Thread	Start coroutine on UI thread	Running on Main
2	Coroutine 2	Dispatchers.IO	IO Thread Pool	Start coroutine on IO thread	Running on IO
3	Coroutine 3	Dispatchers.Default	CPU Thread Pool	Start coroutine on CPU thread	Running on Default
4	All	-	-	Coroutines complete	-

💡 All coroutines finish after printing their messages on their respective threads.

Variable Tracker

Coroutine	Dispatcher	Thread Type	Status
Coroutine 1	Dispatchers.Main	Main/UI Thread	Completed
Coroutine 2	Dispatchers.IO	IO Thread Pool	Completed
Coroutine 3	Dispatchers.Default	CPU Thread Pool	Completed

Key Moments - 3 Insights

Why does Dispatchers.Main run on the UI thread?

Dispatchers.Main is designed to run coroutines on the main thread where UI updates happen, as shown in execution_table step 1.

What kind of tasks should use Dispatchers.IO?

Dispatchers.IO is optimized for blocking IO tasks like reading files or network calls, as seen in step 2 where it runs on an IO thread pool.

When should Dispatchers.Default be used?

Dispatchers.Default is for CPU-intensive tasks that need background threads, demonstrated in step 3 running on CPU thread pool.

Visual Quiz - 3 Questions

Look at the execution_table, which dispatcher runs on the main UI thread?

A Dispatchers.Main

B Dispatchers.IO

C Dispatchers.Default

D Dispatchers.Unconfined

💡 Hint

Check the 'Thread Type' column in execution_table row 1.

At which step does the coroutine run on an IO thread pool?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Dispatcher' and 'Thread Type' columns in execution_table.

If you want to run a CPU-heavy task, which dispatcher should you choose?

A Dispatchers.Main

B Dispatchers.IO

C Dispatchers.Default

D Dispatchers.Unconfined

💡 Hint

Refer to the 'Dispatcher' and 'Thread Type' in execution_table step 3.

Concept Snapshot

Dispatchers.Main runs coroutines on the UI thread for UI updates.
Dispatchers.IO is for blocking IO tasks using a thread pool.
Dispatchers.Default handles CPU-intensive work on background threads.
Choose dispatcher based on task type to keep app responsive.
Coroutines complete after running on their assigned threads.

Full Transcript

When you start a coroutine in Kotlin, you pick a dispatcher to decide which thread it runs on. Dispatchers.Main runs on the main UI thread, perfect for updating the screen. Dispatchers.IO uses a pool of threads for input/output tasks like reading files or network calls. Dispatchers.Default runs on background CPU threads for heavy computations. In the example, three coroutines start on these dispatchers and print messages showing where they run. Each coroutine finishes after its work. This helps keep your app smooth by running tasks on the right threads.