Using the Paged List with Boundary Callback in Android

In this post, I will explain how to use the Android Paged list with a boundary callback. The idea is to see an example where both the network and the local database is involved. We would be using Kotlin for the whole example.

Introduction

In this post, we will be using the Android Paged List to populate a RecyclerView with data from the DB. The DB is populated using network calls. Here’s the flow:

• The RecyclerView will observe the local DB to display the items in the list.
• The calls are paginated ie. at a time 10–20 items are loaded and more items are loaded when the user scrolls down.
• Whenever a boundary condition is met(start/end of the list), a network call is made to fetch new data. The data is fetched and inserted in the DB.
• As the RecyclerView is already observing the DB, it populates the list with new data when required.

Prerequisite

In this article, I will assume that you are using Room persistence in your app. If you want a quick guide on getting started with Room, you can take a look at my post about it.

Dependencies

Add the following library dependencies in the app/build.gradle file. We would be using -ktx dependencies as we are using Kotlin in the app.

implementation "androidx.paging:paging-runtime-ktx:2.1.2"    implementation "androidx.paging:paging-rxjava2-ktx:2.1.2"

Add a Recycler View holder

First, let's add a simple ViewHolder for our RecyclerView. The view holder is the same as what you normally use for your RecyclerView.

Add a Recycler View Adapter

Next, we will add a ListAdapter for our recycler view. Notice, that we extending the PagedListAdapter instead of the RecyclerViewAdapter .

In the adapter, we add a DIFF_CALLBACK object. This is used by the PagedListAdapter to compare two objects and check if they are the same.

Define a Data Source

In your Dao class add a method that returns DataSource.Factory . The paged list will consume this to get items from the DB in a paginated manner.

Define a Boundary Callback

This is the interesting part where we extend PagedList.BoundaryCallback to add a boundary callback for our RecyclerView . This class has three important methods:

• onZeroItemsLoaded : It is triggered when the list has no items.
• onItemAtFrontLoaded: It is triggered when the user scrolls to the top of the list.
• onItemAtEndLoaded: It is triggered when the user scrolls to the end of the list.

For each of these functions, we do an API call to fetch data from the network. Once fetched, the data is inserted into the DB. You can have some other custom logic based on your use-case.

Note: In the example, I am not doing the actual API call but am just using mockGetUsers to get a list of 10 random users.

Next, we will wire up everything.

Setup Live Data

In our MainActivity we will setup live data to observe the DB. Also, we will be setting a boundary callback to trigger network calls when required.

In the above snippet, we are creating an instance of LivePagedListBuilder . Note the following about this object:

• It used a pagedListConfig that defines the size of a page and pre-fetch distance. Pre-fetch distance tells the list the number of items to be fetched initially.
• It is wired to the fetchUsers method of userDao. Remember that fetchUsers returns a DataSource.Factory.
• Finally, we provide an instance of UserBoundaryCallback to trigger the network calls.

Setup the Recycler View

Finally, we will set up the RecyclerView . Notice that the live data is observing the adapter.submitList and apart from this everything is same as what you normally use for a RecyclerView.

Demo

Here’s a GIF of the working sample.

Source Code

You can find the complete source code used in this sample on Github.