If page 1 and 2 were 10 each you load results 21-30 Same as if you are scrolling and have reached result 20 And want to load more.
But the underlying table changed since. I'm not very familiar with these myself, but it seams to me that the best solution is to keep a session cursor for the user, and these are a lot simpler when you only ever move it forward.
It's slightly different but I don't see why there should be a notable difference in difficulty. You need to somehow represent what you saw so far and act based on that.
Curious as to where the line between “addictive feature” and "good UX" is. Is deliberate pagination actual impedance to use or merely an annoyance that's been weeded out with modern UX design? When does a feature that simply makes your product easier to use cross into a territory that it's illegal? What about media previews, in a platform like reddit if you can preview or expand media directly from the main list is t…
The way I see it, it's the incessant stimuli you get through these apps. There's just no point where the screen stays quiet, stimulus free. Moving elements capture our attention naturally, especially when the entire screen keeps moving. The endless scroll element just makes sure that the stimulus keeps getting renewed the moment you're done with it. Instead, a scroll should give you a break before heading into the ne…
The problem with using scrolling as a metric is it assumes satisfaction with the content presented and ignores the fact that, on certain apps, many scroll miles go into skipping around articles or ads or reposts to get to the content you want, and imo a punishment for seeking more content while also diluting said content with forced ads at an alarming ratio is not indicative of addiction but scarcity of satisfaction and engaging content
Infinite scroll evolved alongside algorithms that incentivise addictive content. So it’s “good” UX in that it’s effective for consuming addictive content… When I’m trying to do something constructive, like search or browse, infinite scroll is IMHO disastrously bad. You can’t keep your place in the list, or jump ahead/back.
On the contrary, pagination makes it impossible to keep your place in the list if it changes between page loads.
Ah yes, let me just look at Instagram for the ideal model of infinite scroll UX. You can't even scroll up to something you've actually subscribed to that you didn't mean to scroll past without it tossing it into the memory hole and replacing it with something you don't care about.
Curious as to where the line between “addictive feature” and "good UX" is. Is deliberate pagination actual impedance to use or merely an annoyance that's been weeded out with modern UX design? When does a feature that simply makes your product easier to use cross into a territory that it's illegal? What about media previews, in a platform like reddit if you can preview or expand media directly from the main list is t…
Infinite scroll is bad UX design and always has been.
It makes it impossible to click on any links in the footer of the page or even really reading what's in the footer.
I remember when it was initially introduced, everyone I spoke to about it hated it.
This is exactly why I force my kids to always create accounts as 30-years old (by specifying a birth data in the 90s), to avoid as much State interference as possible.
Did you know that if your child has a "kid" account you cannot follow him on google maps? We had to make one for "adults" in order to be able to do so.
Infinite scroll evolved alongside algorithms that incentivise addictive content. So it’s “good” UX in that it’s effective for consuming addictive content… When I’m trying to do something constructive, like search or browse, infinite scroll is IMHO disastrously bad. You can’t keep your place in the list, or jump ahead/back.
On the contrary, pagination makes it impossible to keep your place in the list if it changes between page loads.
Did you think HN has an unusable and bad interface? It seems to be a remarkably popular website despite having hard pages that change order on every refresh.
The challenge is to retain an ordering over the result set. How would infinite scroll behave any differently in this case? The changing results seems to be an orthogonal concern to pagination/infinite scroll.
Infinite scroll makes the problem much easier, even if it’s still a problem. The only action you need to support is loading more results, which you can do by loading all results and filtering out those already shown. With pagination, the user may say “give me page 3” and you have no idea what was on pages 1 and 2, if they were even loaded.
I mean sure, if you do it that way. But its easy to encode the page starting index and pagenate from there. Its even exactly the same algorithm as infinite scroll.
Curious as to where the line between “addictive feature” and "good UX" is. Is deliberate pagination actual impedance to use or merely an annoyance that's been weeded out with modern UX design? When does a feature that simply makes your product easier to use cross into a territory that it's illegal? What about media previews, in a platform like reddit if you can preview or expand media directly from the main list is t…
Infinite scroll is bad UX design and always has been. It makes it impossible to click on any links in the footer of the page or even really reading what's in the footer. I remember when it was initially introduced, everyone I spoke to about it hated it.
Also creates a confusion that algorithm profiteers love, where before you could know a post you saw would be page 1 today and page 2 tomorrow now the homepage of every app is absolute chaos so you have to spend hours searching for something specific or you're just always seeing exactly what they want you to see (to increase engagement or whatever instead of any sensible order)