Coroutines for async networking in Android Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a coroutine in Kotlin?

A coroutine is a lightweight thread that allows you to write asynchronous, non-blocking code in a sequential style.

beginner

Why use coroutines for networking in Android?

Coroutines help perform network calls off the main thread without blocking the UI, making apps responsive and smooth.

intermediate

What does the 'suspend' keyword mean in Kotlin coroutines?

The 'suspend' keyword marks a function that can pause execution without blocking the thread, allowing other work to run.

beginner

How do you launch a coroutine in Android?

You can launch a coroutine using CoroutineScope.launch, often with Dispatchers.IO for network tasks.

intermediate

What is the role of Dispatchers.IO in coroutines?

Dispatchers.IO is a coroutine dispatcher optimized for offloading blocking IO tasks like network or disk operations.

Which keyword marks a function that can be paused and resumed in Kotlin coroutines?

A suspend

B async

C launch

D delay

The 'suspend' keyword marks functions that can suspend execution without blocking the thread.

Which dispatcher is best suited for network calls in Kotlin coroutines?

A Dispatchers.Default

B Dispatchers.IO

C Dispatchers.Main

D Dispatchers.Unconfined

Dispatchers.IO is optimized for IO-bound tasks like network calls.

What happens if you run a network call on the main thread in Android?

A The app crashes immediately

B The network call runs faster

C The UI freezes and becomes unresponsive

D Nothing special happens

Running network calls on the main thread blocks the UI, causing it to freeze.

Which coroutine builder starts a new coroutine without blocking the current thread?

A runBlocking

B withContext

C async

D launch

'launch' starts a new coroutine and does not block the current thread.

How do you handle the result of an asynchronous network call in coroutines?

A Using suspend functions and returning the result directly

B Using runBlocking everywhere

C Using threads manually

D Using callbacks

Suspend functions allow you to write asynchronous code that returns results directly without callbacks.

Explain how Kotlin coroutines improve networking tasks in Android apps.

Think about how coroutines let you do network calls without freezing the app.

Describe the steps to perform an asynchronous network request using coroutines in Android.

Consider how you start the coroutine, where the network runs, and how you update the UI.

Practice

1. What is the main benefit of using coroutines for network calls in Android apps?

easy

A. They replace the need for any background threads.

B. They make the app run faster by using more CPU cores.

C. They automatically cache network data for offline use.

D. They prevent the app's screen from freezing during network tasks.

Solution

1. Step 1: Understand what happens during network calls

   Network calls can take time and if done on the main thread, they freeze the UI.

2. Step 2: Role of coroutines in network calls

   Coroutines run network tasks in the background, keeping the UI responsive.

3. Final Answer:

   They prevent the app's screen from freezing during network tasks. -> Option D

4. Quick Check:

   Coroutines keep UI responsive = D [OK]

Hint: Coroutines keep UI smooth by running tasks in background [OK]

Common Mistakes:

• Thinking coroutines speed up CPU usage
• Believing coroutines cache data automatically
• Assuming coroutines remove all threading needs

2. Which of the following is the correct way to start a coroutine for a network call on a background thread?

easy

A. launch(Dispatchers.Main) { fetchData() }

B. launch(Dispatchers.Default) { updateUI() }

C. launch(Dispatchers.IO) { fetchData() }

D. launch { fetchData() }

Solution

1. Step 1: Identify dispatcher for background network tasks

   Dispatchers.IO is designed for blocking IO tasks like network calls.

2. Step 2: Match correct coroutine launch syntax

   launch(Dispatchers.IO) { fetchData() } runs fetchData() on IO thread pool.

3. Final Answer:

   launch(Dispatchers.IO) { fetchData() } -> Option C

4. Quick Check:

   Network calls use Dispatchers.IO = B [OK]

Hint: Use Dispatchers.IO for network calls in launch [OK]

Common Mistakes:

• Using Dispatchers.Main for network calls
• Confusing Dispatchers.Default with IO
• Omitting dispatcher and running on main thread

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

fun main() = runBlocking {
  launch(Dispatchers.IO) {
    println("Network call started")
  }
  println("Main thread continues")
}

medium

A. Main thread continues\nNetwork call started

B. Only Network call started

C. Network call started\nMain thread continues

D. Only Main thread continues

Solution

1. Step 1: Understand runBlocking and launch behavior

   runBlocking blocks main thread until all coroutines complete. launch starts coroutine asynchronously.

2. Step 2: Order of print statements

   "Main thread continues" prints immediately; "Network call started" prints shortly after from IO dispatcher.

3. Final Answer:

   Main thread continues\nNetwork call started -> Option A

4. Quick Check:

   launch is async, main prints first = C [OK]

Hint: launch runs async, main prints before coroutine output [OK]

Common Mistakes:

• Assuming launch blocks main thread
• Expecting network print before main print
• Ignoring coroutine dispatchers

4. Identify the error in this coroutine code snippet:

GlobalScope.launch(Dispatchers.IO) {
  val data = fetchData()
  textView.text = data
}

medium

A. fetchData() must be called on Dispatchers.Main.

B. Cannot update UI from Dispatchers.IO thread.

C. GlobalScope cannot be used with launch.

D. textView.text should be assigned inside fetchData().

Solution

1. Step 1: Check thread for UI update

   UI elements like textView must be updated on the main thread.

2. Step 2: Identify misuse of Dispatchers.IO

   Dispatchers.IO runs on background thread; updating UI here causes error.

3. Final Answer:

   Cannot update UI from Dispatchers.IO thread. -> Option B

4. Quick Check:

   UI updates require Dispatchers.Main = A [OK]

Hint: Update UI only on Dispatchers.Main thread [OK]

Common Mistakes:

• Updating UI on background thread
• Misusing GlobalScope without lifecycle awareness
• Calling fetchData() on main thread unnecessarily

5. You want to fetch user data from the network and then update the UI with the result. Which coroutine structure correctly handles this?

hard

A. launch(Dispatchers.Main) { val data = withContext(Dispatchers.IO) { fetchUser() }; updateUI(data) }

B. launch(Dispatchers.IO) { val data = fetchUser(); updateUI(data) }

C. launch { val data = fetchUser(); updateUI(data) }

D. launch(Dispatchers.Default) { val data = fetchUser(); updateUI(data) }

Solution

1. Step 1: Identify correct dispatcher for network call

   Network call fetchUser() should run on Dispatchers.IO to avoid blocking UI.

2. Step 2: Ensure UI update runs on main thread

   updateUI(data) must run on Dispatchers.Main to safely update UI elements.

3. Step 3: Analyze launch(Dispatchers.Main) { val data = withContext(Dispatchers.IO) { fetchUser() }; updateUI(data) } structure

   launch on Main dispatcher, inside withContext(Dispatchers.IO) runs fetchUser(), then UI updates on Main.

4. Final Answer:

   launch(Dispatchers.Main) { val data = withContext(Dispatchers.IO) { fetchUser() }; updateUI(data) } -> Option A

5. Quick Check:

   Network on IO, UI on Main = A [OK]

Hint: Use withContext(IO) inside Main launch for network + UI update [OK]

Common Mistakes:

• Updating UI on IO or Default dispatcher
• Running network call on Main dispatcher directly
• Not switching context for network call