As someone with ADD, I get stuck in scroll loops a lot. If the scrolling had an end, it’s easier to kick my brain out and get it to go do other things.
But if there’s infinite scroll, my brain will happily sit for hours and just scroll through random crap.
Which is more of a problem with my brain, but having interrupted scrolling makes it easier to break the loop.
This. To implement most infinite scrolls UI’s you are still doing pagination with an API,just automatically requesting the next page in the list rather than needing to press a “next” button to kick it off (usually). Most apps and sites could implement switching between pagination UI and Infinite Scroll UI as a setting.
One of those things that would not be a ton of effort, but since it does create two different things to show does increase maintenance efforts for the dev. So I get why people tend to go for one or the other and rarely both, but it’d be a huge win for user preference.
As someone with ADD, I get stuck in scroll loops a lot. If the scrolling had an end, it’s easier to kick my brain out and get it to go do other things.
But if there’s infinite scroll, my brain will happily sit for hours and just scroll through random crap.
Which is more of a problem with my brain, but having interrupted scrolling makes it easier to break the loop.
This. To implement most infinite scrolls UI’s you are still doing pagination with an API,just automatically requesting the next page in the list rather than needing to press a “next” button to kick it off (usually). Most apps and sites could implement switching between pagination UI and Infinite Scroll UI as a setting.
One of those things that would not be a ton of effort, but since it does create two different things to show does increase maintenance efforts for the dev. So I get why people tend to go for one or the other and rarely both, but it’d be a huge win for user preference.