FlowOn for changing dispatcher in Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the flowOn operator in Kotlin Flow?

The flowOn operator changes the dispatcher (thread) on which the upstream flow is executed, allowing you to control where the flow's emissions happen.

intermediate

How does flowOn affect the execution of a Kotlin Flow?

It switches the context for the flow's upstream operations, so the code before flowOn runs on the specified dispatcher, while downstream operations run on the collector's context.

beginner

Which dispatcher is commonly used with flowOn for CPU-intensive tasks?

The Dispatchers.Default dispatcher is commonly used with flowOn for CPU-intensive work.

advanced

Can flowOn be used multiple times in a single flow chain?

Yes, you can use flowOn multiple times to switch dispatchers at different points in the flow chain, affecting the upstream operations before each flowOn.

beginner

What happens if you use flowOn with Dispatchers.IO?

The upstream flow operations run on the IO dispatcher, which is optimized for blocking IO tasks like reading files or network calls.

What does the flowOn operator do in Kotlin Flow?

A Changes the dispatcher for downstream flow operations

B Changes the dispatcher for upstream flow operations

C Cancels the flow

D Collects the flow on the main thread

flowOn changes the dispatcher for upstream operations, not downstream.

If you want to perform heavy CPU work in a flow, which dispatcher should you use with flowOn?

A Dispatchers.Default

B Dispatchers.Main

C Dispatchers.IO

D Dispatchers.Unconfined

Dispatchers.Default is optimized for CPU-intensive tasks.

Where do the downstream flow operations run when you use flowOn?

A On the dispatcher specified in <code>flowOn</code>

B On a new thread created by <code>flowOn</code>

C On the collector's coroutine context

D On the main thread always

Downstream operations run on the collector's coroutine context.

Can you use flowOn more than once in a flow chain?

A Yes, to switch dispatchers at different points

B Yes, but it has no effect after the first use

C No, only once is allowed

D No, it causes an error

flowOn can be used multiple times to change dispatchers upstream at different points.

Which dispatcher is best for IO-bound tasks when used with flowOn?

A Dispatchers.Default

B Dispatchers.Unconfined

C Dispatchers.Main

D Dispatchers.IO

Dispatchers.IO is optimized for blocking IO tasks.

Explain how flowOn changes the execution context of a Kotlin Flow and why this is useful.

Think about where the flow code runs before and after <code>flowOn</code>.

Describe a scenario where using flowOn with Dispatchers.IO would improve your Kotlin Flow's performance.

Consider reading files or network calls.

Practice

1. What does the flowOn operator do in Kotlin Flow?

easy

A. It collects the flow on the main thread.

B. It changes the thread where the flow is executed.

C. It cancels the flow immediately.

D. It buffers the flow emissions.

Solution

1. Step 1: Understand the role of flowOn

   The flowOn operator changes the dispatcher where the upstream flow runs, allowing background work on a different thread.

2. Step 2: Differentiate from other flow operators

   Unlike collection which runs on the original coroutine context, flowOn switches the execution context of the flow itself.

3. Final Answer:

   It changes the thread where the flow is executed. -> Option B

4. Quick Check:

   flowOn switches thread = B [OK]

Hint: Remember: flowOn changes flow thread, not collector thread [OK]

Common Mistakes:

• Confusing flowOn with collect context
• Thinking flowOn cancels the flow
• Assuming flowOn buffers emissions

2. Which of the following is the correct syntax to apply flowOn to a flow named myFlow to run on Dispatchers.IO?

easy

A. myFlow.runOn(Dispatchers.IO)

B. myFlow.collectOn(Dispatchers.IO)

C. myFlow.flow(Dispatchers.IO)

D. myFlow.flowOn(Dispatchers.IO)

Solution

1. Step 1: Identify the correct function name

   The operator to change the dispatcher of a flow is flowOn, not collectOn, flow, or runOn.

2. Step 2: Confirm the syntax usage

   The correct syntax is calling flowOn on the flow instance with the dispatcher as argument.

3. Final Answer:

   myFlow.flowOn(Dispatchers.IO) -> Option D

4. Quick Check:

   Correct syntax = A [OK]

Hint: Use flowOn exactly as method name [OK]

Common Mistakes:

• Using wrong method names like collectOn
• Passing dispatcher incorrectly
• Confusing flowOn with collect

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

flow {
  emit(Thread.currentThread().name)
}.flowOn(Dispatchers.IO)
 .collect { println(it) }

medium

A. The collector runs on the original coroutine context thread.

B. The collector runs on the main thread regardless.

C. The collector runs on Dispatchers.IO thread.

D. The collector runs on a new thread created by flowOn.

Solution

1. Step 1: Understand flowOn effect on upstream

   The flowOn(Dispatchers.IO) changes the thread where the flow builder runs, so emit runs on IO thread.

2. Step 2: Identify collector thread context

   The collector runs on the coroutine context where collect is called, which is the original coroutine context unless changed explicitly.

3. Final Answer:

   The collector runs on the original coroutine context thread. -> Option A

4. Quick Check:

   Collector thread = original context = C [OK]

Hint: flowOn changes upstream thread, collector stays on original [OK]

Common Mistakes:

• Assuming collector runs on flowOn dispatcher
• Thinking flowOn creates new thread for collector
• Confusing emit thread with collect thread

4. Identify the error in this Kotlin Flow code:

flow {
  emit(1)
}.flowOn(Dispatchers.IO)
.collect { value ->
  println(value)
}

medium

A. Missing coroutine scope to call collect.

B. flowOn cannot be used with emit.

C. collect must be called before flowOn.

D. Dispatchers.IO is not a valid dispatcher.

Solution

1. Step 1: Check coroutine context for collect

   The collect function is a suspend function and must be called inside a coroutine or suspend function.

2. Step 2: Verify flowOn and emit usage

   Using flowOn(Dispatchers.IO) with emit is correct; no error here.

3. Final Answer:

   Missing coroutine scope to call collect. -> Option A

4. Quick Check:

   collect needs coroutine scope = D [OK]

Hint: Always call collect inside coroutine or suspend function [OK]

Common Mistakes:

• Thinking flowOn can't be used with emit
• Calling collect outside coroutine
• Misordering flowOn and collect

5. You want to perform a CPU-intensive calculation inside a flow and collect results on the main thread. Which is the correct way to use flowOn and collect to achieve this?

hard

A. Use collectOn(Dispatchers.Default) for calculation and flowOn(Dispatchers.Main) for collection.

B. Use flowOn(Dispatchers.Main) for calculation and collect on Default dispatcher.

C. Use flowOn(Dispatchers.Default) for calculation and collect on main thread.

D. Run calculation and collection both on Dispatchers.IO.

Solution

1. Step 1: Choose dispatcher for CPU-intensive work

   CPU-intensive tasks should run on Dispatchers.Default to avoid blocking main thread.

2. Step 2: Use flowOn to switch flow execution thread

   Applying flowOn(Dispatchers.Default) runs the flow builder on Default dispatcher.

3. Step 3: Collect on main thread

   Collecting on main thread allows UI updates; no dispatcher change needed for collect.

4. Final Answer:

   Use flowOn(Dispatchers.Default) for calculation and collect on main thread. -> Option C

5. Quick Check:

   CPU work on Default, collect on main = A [OK]

Hint: Put heavy work in flowOn(Default), collect on main thread [OK]

Common Mistakes:

• Using flowOn(Main) for heavy work
• Confusing flowOn with collectOn
• Running CPU work on IO dispatcher