Room with Coroutines in Android Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Room in Android development?

Room is a library that provides an abstraction layer over SQLite to allow fluent database access while harnessing the full power of SQLite.

beginner

Why use Coroutines with Room?

Coroutines help perform database operations asynchronously without blocking the main thread, keeping the app responsive.

intermediate

What keyword is used to mark a DAO method as a suspend function?

You use the 'suspend' keyword in Kotlin before the function declaration to mark it as a suspend function for coroutines.

intermediate

How does Room support returning LiveData or Flow?

Room can return LiveData or Flow objects from DAO queries to automatically update the UI when data changes, integrating with coroutines and lifecycle.

beginner

What is the benefit of marking DAO functions with 'suspend'?

Marking DAO functions with 'suspend' allows them to be called from coroutines, enabling non-blocking database operations.

Which keyword is used in Kotlin to make a Room DAO function asynchronous with coroutines?

A await

B async

C defer

D suspend

The 'suspend' keyword marks a function as suspendable, allowing it to be called from coroutines for asynchronous execution.

What does Room provide over SQLite?

A An abstraction layer for easier database access

B A graphical user interface

C Automatic network synchronization

D Built-in cloud storage

Room provides an abstraction layer over SQLite to simplify database operations while keeping full SQLite power.

Which of these is a recommended way to observe database changes with Room and coroutines?

A Returning LiveData or Flow from DAO queries

B Using callbacks only

C Polling the database every second

D Using Thread.sleep()

Returning LiveData or Flow allows automatic updates to UI when data changes, integrating well with coroutines.

What happens if you call a suspend DAO function on the main thread without coroutines?

A It runs asynchronously automatically

B It blocks the UI thread

C It crashes the app

D It runs on a background thread by default

Calling suspend functions without proper coroutine context can block the main thread, causing UI freezes.

Which coroutine builder is commonly used to call suspend Room DAO functions from a ViewModel?

A runBlocking

B async

C launch

D delay

The 'launch' builder starts a coroutine without blocking the main thread, suitable for calling suspend DAO functions.

Explain how Room and Kotlin coroutines work together to perform database operations without freezing the UI.

Think about how suspend functions and coroutine scopes help keep the app responsive.

Describe how you would observe changes in a Room database using Kotlin Flow and update the UI accordingly.

Consider how Flow streams data and how to collect it safely in UI components.

Practice

1. What is the main benefit of using Coroutines with Room in Android development?

easy

A. They replace the need for SQL queries.

B. They automatically create database tables.

C. They allow database operations to run without freezing the app UI.

D. They make the app use less memory.

Solution

1. Step 1: Understand Coroutines role

   Coroutines let tasks run in the background without blocking the main app thread.

2. Step 2: Connect Coroutines with Room

   Room uses suspend functions with Coroutines to perform database operations smoothly without freezing UI.

3. Final Answer:

   They allow database operations to run without freezing the app UI. -> Option C

4. Quick Check:

   Coroutines keep UI responsive = A [OK]

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

Common Mistakes:

• Thinking Coroutines create tables automatically
• Believing Coroutines replace SQL queries
• Assuming Coroutines reduce app memory usage directly

2. Which of the following is the correct way to declare a suspend function in a Room DAO interface?

easy

A. suspend fun getAllUsers(): List<User>

B. fun getAllUsers(): List<User>

C. async fun getAllUsers(): List<User>

D. fun suspend getAllUsers(): List<User>

Solution

1. Step 1: Recall suspend function syntax

   A suspend function is declared with the keyword suspend before fun.

2. Step 2: Check each option

   suspend fun getAllUsers(): List<User> correctly uses suspend fun. Plain fun getAllUsers(): List<User> lacks the suspend keyword. fun suspend getAllUsers(): List<User> has the keywords in wrong order. async fun getAllUsers(): List<User> uses async which is not valid here.

3. Final Answer:

   suspend fun getAllUsers(): List<User> -> Option A

4. Quick Check:

   suspend keyword before fun = B [OK]

Hint: Remember: suspend keyword always comes before fun [OK]

Common Mistakes:

• Placing suspend after fun
• Using async instead of suspend
• Omitting suspend keyword for coroutine functions

3. Given this DAO function:

 @Query("SELECT * FROM users")
 suspend fun getUsers(): List<User>

What happens when you call getUsers() from a coroutine?

medium

A. The function blocks the main thread until data is fetched.

B. The function suspends the coroutine until data is fetched, then returns the list.

C. The function returns immediately with an empty list.

D. The function throws a compile-time error.

Solution

1. Step 1: Understand suspend function behavior

   A suspend function pauses the coroutine without blocking the thread until the result is ready.

2. Step 2: Apply to Room DAO call

   Calling getUsers() suspends the coroutine until Room fetches data, then returns the list.

3. Final Answer:

   The function suspends the coroutine until data is fetched, then returns the list. -> Option B

4. Quick Check:

   suspend functions pause coroutine, not block thread = C [OK]

Hint: Suspend functions pause coroutine, not block main thread [OK]

Common Mistakes:

• Thinking suspend blocks main thread
• Expecting immediate empty list return
• Assuming compile-time error on suspend

4. You wrote this DAO method:

@Query("SELECT * FROM users")
fun getUsers(): List<User>

When calling getUsers() from a coroutine, what problem will occur?

medium

A. The app will crash with a runtime error about main thread database access.

B. The function will suspend correctly and return data.

C. The function will return null instead of data.

D. The function will compile but never return.

Solution

1. Step 1: Identify missing suspend keyword

   The DAO method is not marked suspend, so it runs on the calling thread.

2. Step 2: Understand Room's main thread policy

   Room forbids database queries on the main thread to avoid freezing UI, causing runtime crash if violated.

3. Final Answer:

   The app will crash with a runtime error about main thread database access. -> Option A

4. Quick Check:

   Non-suspend DAO on main thread causes crash = A [OK]

Hint: Always mark DAO queries suspend to avoid main thread crash [OK]

Common Mistakes:

• Forgetting suspend keyword in DAO
• Expecting null return on wrong thread
• Assuming silent failure without crash

5. You want to insert a list of users into the database using Room and Coroutines. Which DAO method signature correctly supports this operation without blocking the UI?

@Insert
??? fun insertUsers(users: List<User>)

hard

A. fun insertUsers(users: List<User>)

B. async fun insertUsers(users: List<User>)

C. fun insertUsers(users: List<User>): Deferred<Unit>

D. suspend fun insertUsers(users: List<User>)

Solution

1. Step 1: Identify correct coroutine support

   To run database operations without blocking UI, DAO methods must be suspend functions.

2. Step 2: Evaluate options

   suspend fun insertUsers(users: List<User>) uses suspend fun, which is correct. fun insertUsers(users: List<User>) blocks UI. fun insertUsers(users: List<User>): Deferred<Unit> returns Deferred which is not standard DAO signature. async fun insertUsers(users: List<User>) uses invalid async keyword.

3. Final Answer:

   suspend fun insertUsers(users: List<User>) -> Option D

4. Quick Check:

   Use suspend fun for non-blocking Room inserts = D [OK]

Hint: Use suspend fun for DAO inserts to keep UI smooth [OK]

Common Mistakes:

• Omitting suspend causing UI freeze
• Using async keyword incorrectly
• Returning Deferred instead of suspend function