Introduction to Room DB

December 17, 2020

Most Android applications require local data storage. In the past years, we have achieved this through the use of SQLite databases. Room is a persistent library that is part of the Android jetpack. It is built on top of SQLite. The room persistent library has many advantages over raw SQLite.


One advantage is that it saves a developer from writing a lot of boilerplate code to create and manage databases. It also provides compile-time validation of SQL queries.

This means that an application won’t compile if there is an SQL query error. This prevents the developer from encountering run time errors.

This article goes through creating an Android application that uses the room persistent library to create and manage SQLite databases. We are going to create a simple ToDo list application. The list will be stored locally using the library.

Without further ado. Let’s dive in!


To follow through with this tutorial, you will need to:

  1. Have Android Studio installed.
  2. Have a basic knowledge of building Android applications.
  3. Have a basic understanding of the Kotlin programming language, SQL, MVVM architecture and Kotlin coroutines.

Let’s get started!

Step 1 — Getting started

In this step, we are going to take a look at what makes up the room database.

The main components are:

  • Entity - An entity is a class that is annotated with the @Entity annotation. This class represents a database table.
  • DAO - A Data Access Object is used to map SQL queries to functions. It’s an interface annotated with the @DAO annotation.
  • Room Database - This class acts as an access point to the SQL database. The class uses the DAO to issue queries to the SQL database.

With that bit of information, let’s start implementing room in our application. First, download the starter application from GitHub.

It’s just a basic Android application with only the UI logic. Our work will be to build the functionality. After downloading, sync the project to download the necessary dependencies.

With that done, let’s now proceed to the main task.

Step 2 — Creating the entity

Create a package named db and add a Kotlin class inside it. As mentioned earlier, this is the class that we will use to define our table, i.e, its name and column properties.

Add the following code to the class.

data class ToDo( @PrimaryKey val content: String)

Since we are going to record a sentence for each to-do item, we only need one field in the table. We annotate the field with @PrimaryKey to declare it the primary key for our table. One important property of the primary key is the autogenerate parameter. It’s a boolean property.

We set it to true when the primary key is a value that can autoincrement. For our case, the primary key is a string provided by the user and we can not apply that property. There are many annotations for table fields. You can read more about the fields here.

Step 3 — Creating the DAO

Now that we have defined our table, let’s go ahead and create functions to query our table. In the db package, create another file and name it DAO.

We need to create three functions. One to get the ToDO list, another to save a ToDo item, and another one to delete a ToDo item.

Add the code below to implement this.

interface Dao {
    fun addItem(todo: ToDo)

    @Query("SELECT * FROM ToDo")
    suspend fun getList()

    @Query("DELETE FROM ToDo WHERE content = :content")
    suspend fun deleteItem(content: String)

The DAO interface has three major annotations used to query the database.

  1. @Insert - This is used to insert data into a table. The item passed in the function that’s annotated with this function is added to the database.
  2. @Query - This is used when one wants to write an SQL statement. It receives an SQL statement as its parameter. We have used this annotation to get all the ToDo items and to delete one item. We use @query to delete an item since there is no particular annotation to delete a single item.
  3. @Delete - This annotation is used to delete the contents of a database.

We have marked the two functions as suspending, so that they do not block the UI.

That’s all we need for the DAO. Let’s now create the database class.

Step 4 — Creating the database class

As mentioned earlier, the database class uses the data access object to issue queries to the database. For this reason, the class must hold a reference to the DAO.

Write the code below in the database class.

abstract class ListDatabase : RoomDatabase(){
    abstract fun Dao(): Dao

    companion object {
        private var INSTANCE: ListDatabase? = null

        fun getDatabase(context: Context): ListDatabase {
            return INSTANCE ?: synchronized(this) {
                val instance = Room.databaseBuilder(
                INSTANCE = instance

The class needs to exhibit the singleton feature. To do this, we declare the class as abstract and then use a companion object housing a function to create the database instance. By singleton, we mean that only one database instance should be created during the lifetime of the application’s process.

Creating multiple instances may lead to errors in data management. To create the instance, we first declare a variable to hold the instance.

Then, in the getDatabase method, we check whether the INSTANCE variable is null. Otherwise we return it if it isn’t null. If null we use the Room.databaseBuilder method to create the database.

In the method, we pass in the application context, database class, and the database name as parameters. We then update the instance variable before returning the instance.

That’s all we need for the database class.

Step 5 — Creating a repository

A repository acts as a single source of truth. It’s mostly used when an application has multiple sources of data i.e. local and remote sources. We don’t really need it in our application but it is a good practice to use it.

Create another kotlin class and name it Repository. The class needs to hold a reference to the data access object.

Add the code below to the class.

class Repository(private val dao: Dao) {
    fun getList() = dao.getList()

    suspend fun addItem(item: ToDo) = dao.addItem(item)

    suspend fun deleteItem(item: String) = dao.deleteItem(item)

We are going to call these functions from the view model.

Step — Finishing up

We are done implementing the room database. What’s left is completing the other components of the applications. This does not need much explanation.

First, go to MAViewModel and add the following in the MAViewModel class.

val items = repository.getList().asLiveData()

fun addItem(item: ToDo) = runBlocking{ repository.addItem(item) }

fun deleteItem(item: String) = runBlocking { repository.deleteItem(item) }

Then navigate to MainActivity and add the code below, right above the onCreate method.

val vm: MAViewModel by viewModels { MAViewModelFactory(initDb()) }

  private fun initDb(): Repository {
    val db = ListDatabase.getDatabase(this)
    return Repository(db.Dao())

This code initializes the database and the view model passing in the required dependencies.

Now we need to add code to respond to the UI.

Add the following statement to the setPositiveButton method of the AlertDialog.


Then add the code snippet below in the onSwiped method of the ItemTouchHelper class.


Lastly, add the code below in the onCreate method to observe and display database contents.

vm.items.observe(this, {
    todoList.adapter = ListAdapter(it)

That’s all! Build and run the application.

This is how the application should look like.

final app


In this article, we have gone through the Room database. What it is, its advantages, and its basic components. We have also seen how Room contributes to and follows the MVVM architecture.

With that, you can now confidently implement room database in a new or existing application. You can find the source code for the full application from GitHub.

Peer Review Contributions by: Linus Muema

About the author

Peter Kayere

Peter Kayere is a first-year undergraduate student at Jomo Kenyatta University of Agriculture and Technology studying Computer Technology. Peter has a great passion in software development particularly mobile web and android application development.

This article was contributed by a student member of Section's Engineering Education Program. Please report any errors or innaccuracies to