haha yeah

Also, in this video i feel like they ignore "keeping the data fresh", i have no clue on how to do that using the data layering technique

I agree I only heard about executors from github samples, now I am using them also

AsyncTask class is deprecated

It is non-trivial, but it is easy to replace. Lets say you're not using a viewmodel. So you have your app (recyclerview) and a datasource/dataprovider (whether local db or network). All you need is to create the LivePagedListBuilder, and a datasource class that adapts to your data provider(db/network). So you have two things in the middle. It's like a recycler view and an adapter to handle your list. Also, the problem isn't a new shiny thing. The problem is wanting to use every new shiny thing. If you have a solution that works the way you want it to, then no need to look at Paging library. My problem with the samples are, they are overly engineered. So it takes a while a strip out the important bits. But you learn some neat code along the way.

I'm asking myself the same thing, or what if some data at the backend has been deleted? I can't find anything online on this subject

Future is Kotlin :)

you can be sure xD

I thought the same. But then I decided to learn kotlin because all the codelabs regarding the new fresh libraries are written in kotlin only...so decided to learn kotlin. I must admit that it is a very good language when it comes to develop Android Apps. So I would recommend to learn it.

there's no doubt on that. It was obvious when they made kotlin official

That is right. But it is very easy to learn Kotlin when you have Java background. And also give up Java is a very long story for every Android enterprise.

why do someone need recyclerview inside nestedscrollview

@@rahulprasad2311 Why is irrelevant. Just answer the question.

@@rahulprasad2311 someone have multiple recyclerViews in an activity/fragment, all of them have horizontal orientation, but last one has vertical orientation, now I have to implement pagination on this recyclerview, so that we have to put all the recyclerviews in a nestedScrollView.

@@salmanhameed9495 Not the way to go, NestedScrollView will consume the vertical scroll and you'll end up with the vertical RecyclerView not recycling any view at all (horizontal RecyclerView will recycle actually). You have to check out Epoxy or another library to implements this sort of nested RecyclerView

@@salmanhameed9495 I've 2 RecyclerView contained in a NestedScrollView and using Paging Library with the last RecyclerView. However, the PageKeyedDataSource always calls loadAfter() method after I submit list to PagedListAdapter although I do not scroll the bottom RecyclerView. How can I resolve this bug?

github.com/googlesamples/android-architecture-components/tree/master/PagingWithNetworkSample Probably you want this. and also you can see almost all Android architecture components example from here: github.com/googlesamples/android-architecture-components

github.com/googlesamples/android-architecture-components/tree/master/PagingWithNetworkSample

For whoever is interested in this, now there is also an exercise on codelab. codelabs.developers.google.com/codelabs/android-paging/index.html?index=..%2F..index#0

Recycleview only creates viewholders that are on screen (well a bit more) but it still has the full list in cache. Here the list that list that recycleview stores in cache is smaller and not only the viewholder that are created.

exactly as Rok Retar said. RecyclerView still contains the whole chunk of the list. With this, I think, you are feeding the recyclerview the data that it needs to display. I think it is very useful when you are getting large data from the internet.

good question TBH. i myself havent found any reason to migrate to kotlin

Koltin is the future.

Cody Liu You are wrong. Koltin is the present.

You don't need to understand.most important is that Google shows how diverse their engineers are

putin carving turkey for dinner.

man its dose not matter if you listen or not, you need them they don't need u

Radu Savutiu me too. When they invent something, they are base on general case, even can suit 90% of use case, but unfortunately we developers are easily falling into the 10%. I am done with them too, I just want something simple and time saving, so I can focus on the business logic, testing, UI, performance, not a complex and bulky framework which I have to re-invest time on so-called “new” or “excited” things, so can be integrated into my own work which cost days...

once you learn Kotlin, you will regret saying that, trust me

You can create unmaintainable enterprise level apps using Java or whatever language. When you learning new stuff they always looks as a mess. Keep going.

@@FabienHerman Say what? !!!

@manideep lanka i feel your pain

@@DannTeBg What do you mean by "you cant even remove items from the list"?

please follow up on "You cant even remove items from the lists". Why?

Google software is always terrible over engineered. Thats the typical result when you hire only the smartest people on the market