Android Paging Library Tutorial using Retrofit

September 19, 2020August 4, 2018 by Belal Khan

Hi folks, after android Jetpack we have many new things to learn. So here is Android Paging Library Tutorial for you. Android Paging Library is an important component of Android Jetpack.

Update: Jetpack Paging 3.0 has been released, check the updated Jetpack Paging 3.0 Tutorial.

Many app displays a large set of data to the users, for example consider the Amazon App, it shows you the list of products, and the app has too many products, but it do not loads all the product at once, it shows you some products, as soon as you reaches the last item of the product list it loads more products. This is called paging.

Android Paging Library Tutorial – Video

If you don’t like reading text and want a visual experience, then here is a complete step by step video series for understanding Android Paging Library.

Why use Paging?

Assume you have more than 1000 items for your list that you are fetching from a backend server. Here are the cons if you are fetching everything at once.

Disadvantages of not using Paging

User do not see all the items at once, but you are fetching everything at once, so it will consume more bandwidth uselessly.
Creating a large List at once uses more system resources resulting in a lagging app and bad user experience.

Advantages of using Paging

You will only load a small chunk from your large data set, it will consume less bandwidth.
The app will use less resources resulting in a smooth app and nice user experience.

Android Paging Library

Android paging library is a component of android jetpack. Remember it is not available by default so we need to add it. It helps us to load data gradually and gracefully in our application’s RecyclerView.

In this Android Paging Library Tutorial I will not tell you about the theoretical things about the library. Because to know this thing you can visit the official documentation. Instead of discussing the theoretical bla bla bla we will learn implementing the library in our application, as the official documentation might confuse you.

Pre-Requisites

Before moving ahead, you should go through these tutorials first, as we are going to use these things.

Using Retrofit in Android: Complete Retrofit Playlist from Scratch.
We will use the Retrofit Library to fetch the data from backend API. The above tutorial discusses about Retrofit and Building API from scratch. So you can check the sereis.
RecyclerView: RecyclerView Tutorial.
We will load the items in a RecyclerView after fetching it from server.
Android ViewModel: Android ViewModel Tutorial.
This is another component from Android Jetpack. It helps us to store UI related data in a more efficient way.

Backend API

The important thing is the Backend API. Though you can also load data from SQLite database using Paging Library, but often the app needs to fetch data from our Backend API. You can go through this complete retrofit tutorial series to learn building an API using PHP and MySQL.

In this tutorial we will not build our own API, but I am going to use a readymade API of StackOverflow. Below is the API link.

https://api.stackexchange.com/2.2/answers?page=1&pagesize=50&site=stackoverflow

In the above API URL we are passing the below parameters.

page: The number of page that we want to fetch.
pagesize: The total number of items that we want in the page.
site: The site from which we want to fetch the data.

The above URL will give the following response.

android paging library tutorial — Android Paging Library Tutorial

The data is coming from StackOverflow, and it has a very very large data set, so you will get may be infinite number of pages.

Now our task is to fetch from the page 1 and load the next page as soon as the user reaches the end of the list. And to do this we will use the Android Paging Library.

Android Paging Library Tutorial

Now let’s get into the real code friends.

Creating a new project

As always we will create a new Android Studio project. I have created an Android Project named Paging Library Tutorial.
Now before moving ahead we will add the required dependencies.

Adding Dependencies

Go to app level build.gradle file and add the following dependencies.

dependencies {

def paging_version = "1.0.0"

def view_model_version = "1.1.0"

def support_version = "27.1.0"

def glide_version = "4.3.1"

implementation fileTree(include: ['*.jar'], dir: 'libs')

implementation "com.android.support:appcompat-v7:$support_version"

implementation 'com.android.support.constraint:constraint-layout:1.1.2'

testImplementation 'junit:junit:4.12'

androidTestImplementation 'com.android.support.test:runner:1.0.2'

androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'

//adding retrofit

implementation 'com.squareup.retrofit2:retrofit:2.4.0'

implementation 'com.squareup.retrofit2:converter-gson:2.4.0'

//adding view model

implementation "android.arch.lifecycle:extensions:$view_model_version"

implementation "android.arch.lifecycle:viewmodel:$view_model_version"

//adding paging

implementation "android.arch.paging:runtime:$paging_version"

//adding recyclerview and cardview

implementation "com.android.support:cardview-v7:$support_version"

implementation "com.android.support:recyclerview-v7:$support_version"

//adding glide

implementation "com.github.bumptech.glide:glide:$glide_version"

annotationProcessor "com.github.bumptech.glide:compiler:$glide_version"

}

After adding all the above required dependencies sync your project and you are good to go. Here we have added a lot of dependencies these are:
Retrofit and Gson: For fetching and parsing JSON from URL.
ViewModel: Android architecture component for storing data.
Paging: The paging library.
RecyclerView and CardView: For building the List.
Glide: For loading image from URL.

Creating Model Class

Now we will create a model class in our project. We need this class to parse the JSON response automatically. We have a really complex nested JSON in the response. So we need many classes to bind the response into respective java class automatically.

Create a file named StackApiResponse.java and write the following code in it.

package net.simplifiedcoding.androidpagingexample;

import java.util.List;

class Owner {

public int reputation;

public long user_id;

public String user_type;

public String profile_image;

public String display_name;

public String link;

}

class Item {

public Owner owner;

public boolean is_accepted;

public int score;

public long last_activity_date;

public long creation_date;

public long answer_id;

public long question_id;

}

public class StackApiResponse {

public List<Item> items;

public boolean has_more;

public int quota_max;

public int quota_remaining;

}

The above code is pretty simple, I am not using getters and setters just to make it concise and small. The variable names are matching with the JSON keys so the Gson will map the data accordingly.
The above file have only one public class (and actually we can have only one public class in a file). The class named StackApiResponse contains the following json.

Inside the class we are mapping the above JSON object, that is why we have only 4 properties inside StackApiResponse.
Then first item inside StackApiResponse is items which contains an array of items, that is why I have a List<Item>, then has_more is boolean and quota_max and quota_remaining.
Now inside item we have the following JSON.

Android Paging Library Tutorial 1 — Android Paging Library Tutorial

Inside item we have another object named owner, that is why I have created another class named Owner, and I have declared an object of type Owner inside the Item class. I hope you got how we define model class for the specified JSON.

Creating Retrofit Singleton Class

Each time when we want to fetch data from a new page, we need the Retrofit object. So creating a singleton instance of Retrofit is a good idea.
For the singleton instance I will create a new class named RetrofitClient.

package net.simplifiedcoding.androidpagingexample;

import okhttp3.OkHttpClient;

import retrofit2.Retrofit;

import retrofit2.converter.gson.GsonConverterFactory;

public class RetrofitClient {

private static final String BASE_URL = "https://api.stackexchange.com/2.2/";

private static RetrofitClient mInstance;

private Retrofit retrofit;

private RetrofitClient() {

retrofit = new Retrofit.Builder()

.baseUrl(BASE_URL)

.addConverterFactory(GsonConverterFactory.create())

.build();

}

public static synchronized RetrofitClient getInstance() {

if (mInstance == null) {

mInstance = new RetrofitClient();

}

return mInstance;

}

public Api getApi() {

return retrofit.create(Api.class);

}

The above code is pretty simple, if you are having trouble understanding it, then you should first follow the Retrofit Tutorial.

Creating API

Now we will create the API call interface.
Create an interface named Api and write the following code.

package net.simplifiedcoding.androidpagingexample;

import retrofit2.Call;

import retrofit2.http.GET;

import retrofit2.http.Query;

public interface Api {

@GET("answers")

Call<StackApiResponse> getAnswers(@Query("page") int page, @Query("pagesize") int pagesize, @Query("site") String site);

}

Creating RecyclerView

As I already told you that, we will display the list in the RecyclerView. So let’s build the RecyclerView.

Come inside activity_main.xml and define your RecyclerView here.

<?xml version="1.0" encoding="utf-8"?>

<android.support.constraint.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android"

xmlns:app="http://schemas.android.com/apk/res-auto"

xmlns:tools="http://schemas.android.com/tools"

android:layout_width="match_parent"

android:layout_height="match_parent"

tools:context=".MainActivity">

<android.support.v7.widget.RecyclerView

android:id="@+id/recyclerview"

android:layout_width="match_parent"

android:layout_height="match_parent" />

</android.support.constraint.ConstraintLayout>

Now for the RecyclerView create one more layout resource file named recyclerview_users.xml and write the following xml code.

<?xml version="1.0" encoding="utf-8"?>

<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"

android:layout_width="match_parent"

android:layout_height="wrap_content">

<ImageView

android:id="@+id/imageView"

android:layout_width="70dp"

android:layout_height="70dp" />

<TextView

android:id="@+id/textViewName"

android:layout_width="match_parent"

android:layout_height="wrap_content"

android:layout_centerVertical="true"

android:layout_marginLeft="15dp"

android:layout_toRightOf="@id/imageView"

android:text="Belal Khan"

android:textAppearance="@style/Base.TextAppearance.AppCompat.Large"

android:textColor="@color/colorDefault" />

<TextView

android:layout_width="match_parent"

android:layout_height="1dp"

android:layout_below="@id/imageView"

android:background="@color/colorDefault" />

</RelativeLayout>

Creating PagedListAdapter

We need to fetch the data page wise, so this time we will not use the RecyclerView.Adapter but we will use a PagedListAdapter.

What is PagedListAdapter?

It is a class that has the common behaviours needed for a PagedList for example Item Counting, Page CallBack etc. And don’t get too much confused, the only point here is that this is going to be the adapter for our RecyclerView.

Create a class named ItemAdapter and write the following code.

package net.simplifiedcoding.androidpagingexample;

import android.arch.paging.PagedListAdapter;

import android.content.Context;

import android.support.annotation.NonNull;

import android.support.v7.util.DiffUtil;

import android.support.v7.widget.RecyclerView;

import android.view.LayoutInflater;

import android.view.View;

import android.view.ViewGroup;

import android.widget.ImageView;

import android.widget.TextView;

import android.widget.Toast;

import com.bumptech.glide.Glide;

public class ItemAdapter extends PagedListAdapter<Item, ItemAdapter.ItemViewHolder> {

private Context mCtx;

ItemAdapter(Context mCtx) {

super(DIFF_CALLBACK);

this.mCtx = mCtx;

}

@NonNull

@Override

public ItemViewHolder onCreateViewHolder(@NonNull ViewGroup parent, int viewType) {

View view = LayoutInflater.from(mCtx).inflate(R.layout.recyclerview_users, parent, false);

return new ItemViewHolder(view);

}

@Override

public void onBindViewHolder(@NonNull ItemViewHolder holder, int position) {

Item item = getItem(position);

if (item != null) {

holder.textView.setText(item.owner.display_name);

Glide.with(mCtx)

.load(item.owner.profile_image)

.into(holder.imageView);

}else{

Toast.makeText(mCtx, "Item is null", Toast.LENGTH_LONG).show();

}

private static DiffUtil.ItemCallback<Item> DIFF_CALLBACK =

new DiffUtil.ItemCallback<Item>() {

@Override

public boolean areItemsTheSame(Item oldItem, Item newItem) {

return oldItem.question_id == newItem.question_id;

}

@Override

public boolean areContentsTheSame(Item oldItem, Item newItem) {

return oldItem.equals(newItem);

}

};

class ItemViewHolder extends RecyclerView.ViewHolder {

TextView textView;

ImageView imageView;

public ItemViewHolder(View itemView) {

super(itemView);

textView = itemView.findViewById(R.id.textViewName);

imageView = itemView.findViewById(R.id.imageView);

}

The adapter is almost same as RecyclerView.Adapter<>, the only change here is we have a DIFF_CALLBACK implementation that we are passing to the super(). This callback is used to differentiate two items in a List.
For the PagedListAdapter<> we define the Item and the ViewHolder. Item is the item that you want to display, and we already have a class named Item that contains the data that we need to display.

Creating Item Data Source

Now here comes the very important thing, the data source of our item from where we will fetch the actual data. And you know that we are using the StackOverflow API.

For creating a Data Source we have many options, like ItemKeyedDataSource, PageKeyedDataSource, PositionalDataSource. For this example we are going to use PageKeyedDataSource, as in our API we need to pass the page number for each page that we want to fetch. So here the page number becomes the Key of our page.

Create a class named ItemDataSource and write the following code.

package net.simplifiedcoding.androidpagingexample;

import android.arch.paging.PageKeyedDataSource;

import android.support.annotation.NonNull;

import android.util.Log;

import retrofit2.Call;

import retrofit2.Callback;

import retrofit2.Response;

public class ItemDataSource extends PageKeyedDataSource<Integer, Item> {

//the size of a page that we want

public static final int PAGE_SIZE = 50;

//we will start from the first page which is 1

private static final int FIRST_PAGE = 1;

//we need to fetch from stackoverflow

private static final String SITE_NAME = "stackoverflow";

//this will be called once to load the initial data

@Override

public void loadInitial(@NonNull LoadInitialParams<Integer> params, @NonNull final LoadInitialCallback<Integer, Item> callback) {

RetrofitClient.getInstance()

.getApi().getAnswers(FIRST_PAGE, PAGE_SIZE, SITE_NAME)

.enqueue(new Callback<StackApiResponse>() {

@Override

public void onResponse(Call<StackApiResponse> call, Response<StackApiResponse> response) {

if (response.body() != null) {

callback.onResult(response.body().items, null, FIRST_PAGE + 1);

}

@Override

public void onFailure(Call<StackApiResponse> call, Throwable t) {

}

});

}

//this will load the previous page

@Override

public void loadBefore(@NonNull final LoadParams<Integer> params, @NonNull final LoadCallback<Integer, Item> callback) {

RetrofitClient.getInstance()

.getApi().getAnswers(params.key, PAGE_SIZE, SITE_NAME)

.enqueue(new Callback<StackApiResponse>() {

@Override

public void onResponse(Call<StackApiResponse> call, Response<StackApiResponse> response) {

//if the current page is greater than one

//we are decrementing the page number

//else there is no previous page

Integer adjacentKey = (params.key > 1) ? params.key - 1 : null;

if (response.body() != null) {

//passing the loaded data

//and the previous page key

callback.onResult(response.body().items, adjacentKey);

}

@Override

public void onFailure(Call<StackApiResponse> call, Throwable t) {

}

});

}

//this will load the next page

@Override

public void loadAfter(@NonNull final LoadParams<Integer> params, @NonNull final LoadCallback<Integer, Item> callback) {

RetrofitClient.getInstance()

.getApi()

.getAnswers(params.key, PAGE_SIZE, SITE_NAME)

.enqueue(new Callback<StackApiResponse>() {

@Override

public void onResponse(Call<StackApiResponse> call, Response<StackApiResponse> response) {

if (response.body() != null) {

//if the response has next page

//incrementing the next page number

Integer key = response.body().has_more ? params.key + 1 : null;

//passing the loaded data and next page value

callback.onResult(response.body().items, key);

}

@Override

public void onFailure(Call<StackApiResponse> call, Throwable t) {

}

});

}

You might find the above code a little tricky, but it is the most important part of our project. So let’s try to understand it.

We extended PageKeyedDataSource<Integer, Item> in the above class. Integer here defines the page key, which is in our case a number or an integer. Every time we want a new page from the API we need to pass the page number that we want which is an integer. Item is the item that we will get from the API or that we want to get. We already have a class named Item.
Then we defined the size of a page which is 50, the initial page number which is 1 and the sitename from where we want to fetch the data. You are free to change these values if you want.
Then we have 3 overridden methods.
- loadInitials(): This method will load the initial data. Or you can say it will be called once to load the initial data, or first page according to this example.
- loadBefore(): This method will load the previous page.
- loadAfter(): This method will load the next page.

Creating Item Data Source Factory

We are going to use MutableLiveData<> to store our PageKeyedDataSource and for this we need a DataSource.Factory.

package net.simplifiedcoding.androidpagingexample;

import android.arch.lifecycle.MutableLiveData;

import android.arch.paging.DataSource;

import android.arch.paging.PageKeyedDataSource;

public class ItemDataSourceFactory extends DataSource.Factory {

//creating the mutable live data

private MutableLiveData<PageKeyedDataSource<Integer, Item>> itemLiveDataSource = new MutableLiveData<>();

@Override

public DataSource<Integer, Item> create() {

//getting our data source object

ItemDataSource itemDataSource = new ItemDataSource();

//posting the datasource to get the values

itemLiveDataSource.postValue(itemDataSource);

//returning the datasource

return itemDataSource;

}

//getter for itemlivedatasource

public MutableLiveData<PageKeyedDataSource<Integer, Item>> getItemLiveDataSource() {

return itemLiveDataSource;

}

Creating ViewModel

Now create a class named ItemViewModel and write the following code.

package net.simplifiedcoding.androidpagingexample;

import android.arch.lifecycle.LiveData;

import android.arch.lifecycle.ViewModel;

import android.arch.paging.LivePagedListBuilder;

import android.arch.paging.PageKeyedDataSource;

import android.arch.paging.PagedList;

public class ItemViewModel extends ViewModel {

//creating livedata for PagedList and PagedKeyedDataSource

LiveData<PagedList<Item>> itemPagedList;

LiveData<PageKeyedDataSource<Integer, Item>> liveDataSource;

//constructor

public ItemViewModel() {

//getting our data source factory

ItemDataSourceFactory itemDataSourceFactory = new ItemDataSourceFactory();

//getting the live data source from data source factory

liveDataSource = itemDataSourceFactory.getItemLiveDataSource();

//Getting PagedList config

PagedList.Config pagedListConfig =

(new PagedList.Config.Builder())

.setEnablePlaceholders(false)

.setPageSize(ItemDataSource.PAGE_SIZE).build();

//Building the paged list

itemPagedList = (new LivePagedListBuilder(itemDataSourceFactory, pagedListConfig))

.build();

}

Now before moving ahead rebuild your project.

Displaying the Paged List

Finally come inside MainActivity.java and write the following code.

package net.simplifiedcoding.androidpagingexample;

import android.arch.lifecycle.Observer;

import android.arch.lifecycle.ViewModelProvider;

import android.arch.lifecycle.ViewModelProviders;

import android.arch.paging.PagedList;

import android.support.annotation.Nullable;

import android.support.v7.app.AppCompatActivity;

import android.os.Bundle;

import android.support.v7.widget.LinearLayoutManager;

import android.support.v7.widget.RecyclerView;

import android.widget.Toast;

import retrofit2.Call;

import retrofit2.Callback;

import retrofit2.Response;

import retrofit2.Retrofit;

import retrofit2.converter.gson.GsonConverterFactory;

public class MainActivity extends AppCompatActivity {

//getting recyclerview

private RecyclerView recyclerView;

@Override

protected void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState);

setContentView(R.layout.activity_main);

//setting up recyclerview

recyclerView = findViewById(R.id.recyclerview);

recyclerView.setLayoutManager(new LinearLayoutManager(this));

recyclerView.setHasFixedSize(true);

//getting our ItemViewModel

ItemViewModel itemViewModel = ViewModelProviders.of(this).get(ItemViewModel.class);

//creating the Adapter

final ItemAdapter adapter = new ItemAdapter(this);

//observing the itemPagedList from view model

itemViewModel.itemPagedList.observe(this, new Observer<PagedList<Item>>() {

@Override

public void onChanged(@Nullable PagedList<Item> items) {

//in case of any changes

//submitting the items to adapter

adapter.submitList(items);

}

});

//setting the adapter

recyclerView.setAdapter(adapter);

}

Now you are done and you can try running your application.
If everything is fine you will see the below output.

As you can see it is working fine, and we have a smooth and huge list in our application.

Note: If you are not seeing any item, make sure the API URL is working correctly, by opening the URL in your browser, as sometimes stackoverflow blocks the continuous requests to their URLs.

Android Paging Library Tutorial Source Code

This tutorial is very big, and little complicated. So you have to follow all the steps carefully. But for some reason if you are not able to make it you can try with my source code as well.

From the below link you can download my source code on GitHub.

Android Paging Library Tutorial Code

Get the Source Code

So that is all for this Android Paging Library Tutorial friends. I hope you found it helpful, so for a payback (just kidding) please share this tutorial with your friends learning android. And for any question feel free to comment. Thank You 🙂

Belal Khan

Hi, my name is Belal Khan and I am a Google Developers Expert (GDE) for Android. The passion of teaching made me create this blog. If you are an Android Developer, or you are learning about Android Development, then I can help you a lot with Simplified Coding.

Checkout these tutorials as well:

40 thoughts on “Android Paging Library Tutorial using Retrofit”

Sk zafar
August 5, 2018 at 5:30 pm
Hum Firebase database se v paging kar sakte hai kya?? Qki mai apne app mei firebase realtime database hi use kar rha hoon or mujhe v paging implement karna hai, plz help
Reply
Taru Khan
August 6, 2018 at 6:46 am
Hello, I am not able to find your GitHub link related to this tutorial..
Reply
Arnold
August 6, 2018 at 7:39 pm
Awesome..but the link to github is broken 🙂
Reply
- Belal Khan
  August 7, 2018 at 2:33 pm
  Updated the link.
  Reply
Louis
August 7, 2018 at 6:09 am
If you customize the page size, makeit 10 e.g , the app loads only two pages and stops making more data calls.
Reply
- Belal Khan
  August 7, 2018 at 2:28 pm
  That is because it is not our own API, when you send quick multiple request to stackoverflow api it bans your IP address for a while. If you will use your own backend server you will not face this issue.
  Reply
  - Louis
    August 7, 2018 at 6:00 pm
    Makes sense
    Reply
Arnold
August 9, 2018 at 7:08 pm
Very awesome. What if the user connection us halted while scrolling, how can you show a message that data cant be loaded, or a loading progress when we load new page
Reply
Mohammad Irshad Sheikh
August 29, 2018 at 1:45 pm
is there any way to remove a particular item
Reply
- firat
  May 9, 2020 at 11:38 pm
  did you find any solution?
  Reply
  - Mahdi
    July 4, 2020 at 11:33 am
    I’m also looking for a solution
    If anyone see this message by accident let me know how you solved this issue please
    m.javaherisaber@gmail.com
    Reply
Steep
September 1, 2018 at 11:57 am
Let me know how can I send value(i.e parameters) to API which stored in Shared preferences(it needs context)
I need to send access token which is stored in shared preferences
Also let me know how to display no data available toast after hasMore value is false, (Toast needs context)
How can I pass context to ItemDataSource.class ?
Reply
Mohamad Seyedi
October 23, 2018 at 9:49 am
Hello dear bellal khan. I am Mohamad from Iran.
I wanna ask what can I do if I want a pass a @Path or @Field paramater in addition of @Query with retrofit request in DataSource class?
TNX…:D
Reply
- Manuel
  June 7, 2019 at 12:08 pm
  Hi Mohamad, in case you want 1to make a Retrofit request with a specific path you would have to do something like this:
  @GET(/some_url/{my_path})
  Call getResponse(@Path(“my_path”) String path );
  In case it is a field you want to pass it’s even easier, let’s suppose it is a list of items you want to pass
  @POST(/some_url/)
  Call getResponse(@Field(“item_list”) List list );
  Reply
Marco
November 16, 2018 at 11:26 am
Best tutorial for Paging + Retrofit!
Just a side note: like the previous comment, I need to pass the context to the data source factory, for retrieving the access token from the shared preferences. How can i possibly do that?
Thanks!
Reply
Tej
November 19, 2018 at 5:31 am
Thanks for this simplified explanation. I have implemented this successfully.
But my LoadBefore function in DataSource is never being called.
//this will load the previous page
@Override
public void loadBefore(@NonNull final LoadParams params, @NonNull final LoadCallback callback) {
RetrofitClient.getInstance()
Other functions are working successfully. loadAfter function is working fine as per the page size. Facing issue only with LoadBefore function
Reply
Pankaj Pathak
December 4, 2018 at 4:45 am
Hello Sir, Really Awesome , but how to implement a progressbar and reload button if i am using this in a fragment. Unable to find any solution.
Reply
Parthiban
December 5, 2018 at 9:07 am
Hi,
Recyclerview is not updating the list after callback.onResult() called. Please do the needful.
Reply
- Talha
  March 13, 2019 at 1:27 pm
  Awesone tutorial,please make tutorial on pagination with network and database.
  Reply
Parthiban
December 5, 2018 at 9:09 am
Hi,
Recyclerview is not updating the list after callback.onResult called. Please do the needful.
Reply
SUH
January 27, 2019 at 3:43 am
Nice tutorial!
Any idea how we can insert native ads efficiently while using this paging library. I mean since vase data is being loaded in chunks, native ads will also have to be added according to the size of this chunk. I just can’t figure out how to do that efficiently.
Any help would be a great help.
Thanks
Reply
- Belal Khan
  February 22, 2019 at 12:09 pm
  Will try to post a detailed tutorial explaining this.
  Reply
Bhargav B.L
February 6, 2019 at 1:03 pm
Thanx for the tutorial. I’m a big fan of your page.
Is it possible to change URL dynamically from mainactivity(i.e user actions) in this project..?
Can we add filtering and sorting options w.r.t user choice in this project??
Waiting for a positive response…
Thank you
Reply
- Belal Khan
  February 22, 2019 at 12:01 pm
  Use different retrofit objects for your calls.
  Reply
Arif
February 14, 2019 at 7:06 am
showing a white blank screen
if i hit url on browser then this error occur
{“error_id”:400,”error_message”:”site is required”,”error_name”:”bad_parameter”}
Reply
- Belal Khan
  February 22, 2019 at 11:56 am
  You forget to pass the sitename parameter check you code.
  Reply
Kishoe Reddy
March 28, 2019 at 6:34 am
Hi,
Recyclerview is not updating the list after callback.onResult called. Please do the needful.
Reply
Kishoe Reddy
March 28, 2019 at 10:34 am
Is there anyway to clear hole data in one button click.
Reply
Salman Hameed
May 24, 2019 at 10:18 am
I got data ItemDataSource but in my activity it gives me zero length list, I’m just mapping this example to my project , not exactly copy and paste the code.
In my activity onDataChange() call first then it call loadInitial,
Reply
Abbasali
May 29, 2019 at 6:40 am
Hello,
Thanks for the tutorial.
According to my understanding if we are passing number of pages in the api call. We can do it without paging library too as per my understanding we can do it by on page scroll or respective method on scroll we can call api. And is it possible without passing number of items to be displayed. Like we receive full data first and it gets stored in the model then it gets displayed as soon we scroll. As making api calls again and again is efficient way.?
Reply
- Belal Khan
  May 31, 2019 at 4:49 am
  Yes obviously it is efficient. Imagine you have more than 100,000 items in your database. Fetching them all at once with a single api call is the worse thing you can do. If you don’t trust me, try Fetching this amount of data and you will understand.
  Reply
Chinh
January 10, 2020 at 6:43 am
Hello;
Thanks for the tutorial.
Could you tell why you need to FIRST_PAGE + 1 in loadInitial method. I try to keep FIRST_PAGE.It has nothing changed.
, and when i saw data loaded on UI, it was duplicate.
Reply
- Belal Khan
  March 14, 2020 at 3:50 am
  We load first page in the loadInitial() method.
  Reply
wasim mullick
February 20, 2020 at 1:15 pm
Can you please make this tutorial for Kotlin
Reply
- Belal Khan
  March 14, 2020 at 3:36 am
  Yes ofcourse, you will get the kotlin version soon.
  Reply
  - Pavan Kumar Devara
    August 5, 2020 at 4:43 am
    Can you show how to add a progress bar whenever new page is called?
    Reply
Sampson
May 19, 2020 at 1:12 pm
Hello… Please how do i implement a search or filter using the pagination library
Reply
nitesh
June 23, 2020 at 7:05 pm
itemPagedList = LivePagedListBuilder(merchentDataSourcefactor!!, pagedListConfig)
.build()
Log.e(“itemPagedList”, “__________________________________” + itemPagedList?.value)
why display null value sir
Reply
Waqar Vicky
July 10, 2020 at 1:18 pm
Like your tutorial. Please make a tutorial about room with paging and retrofit in java.
Reply
Pinkesh Machhi
July 15, 2021 at 11:31 am
You forget to say about INTERNET permission in the manifest.
Reply

Android Paging Library Tutorial using Retrofit

Android Paging Library Tutorial – Video

Why use Paging?

Disadvantages of not using Paging

Advantages of using Paging

Android Paging Library

Pre-Requisites

Backend API

Android Paging Library Tutorial

Creating a new project

Adding Dependencies

Creating Model Class

Creating Retrofit Singleton Class

Creating API

Creating RecyclerView

Creating PagedListAdapter

What is PagedListAdapter?

Creating Item Data Source

Creating Item Data Source Factory

Creating ViewModel

Displaying the Paged List

Android Paging Library Tutorial Source Code

Related

Checkout these tutorials as well:

40 thoughts on “Android Paging Library Tutorial using Retrofit”

Leave a Comment Cancel reply