Dispatcher Main in Kotlin

Introduction

Dispatcher Main is a fundamental concept every Kotlin developer should understand. Dispatchers decide which thread pool runs coroutine code — Main for UI, IO for blocking work, and Default for CPU-bound tasks.

Dispatchers.Main runs coroutines on UI thread in Android/UI apps. In this tutorial you will learn the syntax, walk through a complete example program, study the sample output, and review best practices so you can apply the concept confidently in your own projects.

Definition

• Dispatchers.Main runs coroutines on UI thread in Android/UI apps.
• In console JVM examples, it may fallback to immediate/default behavior.
• Use for UI updates in Android applications.

Syntax

launch(Dispatchers.Main) { }

Dispatcher Main in Kotlin Example Program in Kotlin

import kotlinx.coroutines.*

fun main(args: Array<String>) = runBlocking {
    launch(Dispatchers.Default) {
        println("Running on ${Thread.currentThread().name}")
    }
}

Sample Output

Running on DefaultDispatcher-worker-1

When to use

Switch dispatchers when moving between UI updates (Main) and blocking or CPU-heavy work (IO / Default).

How it works

1. The program starts with a main function — the entry point that runs when you execute the file.

2. launch(Dispatchers.Default) { shows coroutine-based concurrency — work runs without blocking the calling thread.

3. The println("Running on ${Thread.currentThread().name}") statement writes a line to the console — this produces part of the sample output below.

4. Dispatchers.Main runs coroutines on UI thread in Android/UI apps.

5. Run the program in IntelliJ IDEA, Android Studio, or with the Kotlin command-line compiler (kotlinc / kotlin). Compare your console output with the sample output shown below.

Best Practices

• Understand the core idea: dispatchers.Main runs coroutines on UI thread in Android/UI apps.
• Prefer readable names and small functions so examples map directly to real projects.
• Run and modify the example — change values and observe how the output changes.

Common Mistakes

• Skipping the example and only reading the definition — hands-on practice cements the concept.
• Copying syntax without understanding nullable vs non-nullable types or scope rules.
• Ignoring compiler warnings that often point to safer alternatives.

Key Points

• Dispatchers.Main runs coroutines on UI thread in Android/UI apps.
• In console JVM examples, it may fallback to immediate/default behavior.
• Use for UI updates in Android applications.
• Test the example locally and verify the output matches the sample.
• Experiment by changing input values to see how behaviour changes.

Notes

• Add the kotlinx-coroutines-core dependency when running coroutine examples outside Android or IntelliJ.
• Semicolons at the end of statements are optional in Kotlin.