Hell yeah!! Hahaha what a day for you to find these videos huh 😉

Welcome to the channel and excited to have you learn :)

When the list ends, there is nothing more to page so the job is "done" so to speak. This can also be detected when the meta.next value is equal to null. Regarding error handling, you can implement a auto-retry feature to attempt the call that failed 1-3 times (or however many times you want) or you can add something to the UI that mentions a failure in loading and the user can click a button or something to trigger the request. The tutorial was meant to be a simpler and mostly working approach as opposed to a fully bulletproof mechanic. The content is more consumable that way, but some bits of what you mentioned are correct. If you'd like to open a pull request enhancing the functionality, I would review it and make content about me reviewing it!

Perhaps you're right, I just want to see the subtleties of use

@neyasbit I could enhance this over time

The pagination libraries are nice, but limiting at times. If you can roll your own custom implementation for things, I would recommend it! Hope this helps

@@TheAndroidFactory yeap, btw, if api supports offset instead of page, these codes also can work or not? I don't have time now, but I will try to implement later, just wanna ask to be ensure

Yeah absolutely! It would need to change a little bit, but instead of calculating page number, you would just look up how many characters there are, and that is your offset key

@@TheAndroidFactory okay, thanks. I will try

I believe I understand. And the answer likely is: "it depends". When you have a screen that should react "as a whole" I like this pattern, but if you had a screen that held many different data points and ways for the user to interact, it may be better to separate them out. Then again, you could have all of those elements of state in a single data class that has everything you need, and at that point it would boil down to listening for N different pieces of state or having one piece of state that contains N elements. In most cases it may not matter which approach you go with, but sometimes this way or the way you're asking about is better for the use case. Good to be aware of all the options so you can make the best decision when the time comes! Hope that helps haha

@@TheAndroidFactory Im way less expirienced than you(2 years but 1 year work expirience with old old android 13y old code in that company, i started learning jetpack compose 1 year ago) so now i have one more thing to keep in mind i think i understand you a little because in my case i have a screen where ill have a list with some clients info and after i click on it i will have more of clients details so this is all about the screen i guess your way with state is great then ? and i actually wanted to implement some paginating (also custom i didnt want to rely on library i wanted to expand my understanding of android etc). And i managed to get to your video so im thinking to redo my whole screen , i managed to implement some pagination by having lastLoadedId variable in my repository then i gave it value lastLoadedClientId = clientList.last().clientId , so i have two functions one for initialLoading with limit of 7 and the other is loadMore with limit of 4 with .startAfter(lastLoadedClientId) ( im using firebase for this app) , so i made it work somehow and i didnt know if its a good way of doing(i think it is not thats why im trying to find some other solutions). Im talking too much haha , thank you for your response anyway :D

@@TheAndroidFactory if i understood good in my case this will be good since i also have screen with a list of clients( 3 fields displaying on a card) after i click im opening clients info screen where i can see more fields about him and a picture. i wanted to implement a custom pagination because i didnt want to rely on library , so i found you at the right time :D also i did some i think bad way of paginating and thats why i want to find more solutions private var lastLoadedClientId: String? = null in my repository than i have initialLoad fun where i limit 7 items to load and give the lastLoadedClientId = clientList.last().clientId and i have another function which will be called multiple times as long i have items to load loadMore with limit of 4 items and .startAfter(lastLoadedClientId) and giving also value lastLoadedClientId = clientList.last().clientId . Im using firebase , and from my ui i had some similar logic to your to detect when to call loadMore function . Hope i explained well to you :D thanks for any answers

@@TheAndroidFactory i tried few times to reply and is my comment too long? and cant be posted ( it is posted but then dissapears hmm)

if i understood good in my case this will be good since i also have screen with a list of clients( 3 fields displaying on a card) after i click im opening clients info screen where i can see more fields about him and a picture. i wanted to implement a custom pagination because, also i did some i think bad way of paginating and thats why i want to find more solutions private var lastLoadedClientId: String? = null in my repository than i have initialLoad fun where i limit 7 items to load and give the lastLoadedClientId = clientList.last().clientId and i have another function which will be called multiple times as long i have items to load loadMore with limit of 4 items and .startAfter(lastLoadedClientId) and giving also value lastLoadedClientId = clientList.last().clientId . Im using firebase , and from my ui i had some similar logic to your to detect when to call loadMore function . Hope i explained well to you :D thanks for any answers

Yeah I prefer to not use libraries if you don't need to. There's a bunch of fluff by incorporating the library to your project and this was just a simple example of a "custom" solution. The library works, but I've run into limitations with it before that were super annoying to "hack" around, so having full control is sometimes easier. Nothing wrong with using the lib though!

Why - 10 being used?

Just a random number I selected. We want to fetch the next page when the user is 10 items away from the bottom. If we chose a smaller number like 5 or 3, the users may hit the bottom of the current page before the next page has been loaded from the internet. Google's recommended approach under the hood is much larger than just 10! It's mostly a best guess to try and keep the "infinite scroll" feeling truly infinite

Can we deep dive more into this...?

Sure, how so?