3 ms·
Infinite scroll is frustrating on higher latency connections, which I have all the time being here in Australia. Particularly when you want to skip towards the
by lathiat 8y ago
Infinite scroll is frustrating on higher latency connections, which I have all the time being here in Australia.
Particularly when you want to skip towards the end of the list. YouTube has recently changed all their playlists etc to infinite scroll and it takes FOREVER to scroll 5 pages down to get to the bottom of the list. And they don't have a UI to reverse the list order or jump ahead.
They did recently add a list reverse to some places but it's still missing in others. Drives me bonkers :(
Of course it's not necessarily purely the fault of infinite scroll, there are potentially ways to combine them. But the basic pattern many places implement is painful for this latency and no skip-ahead combination.
- NullPrefix 8y ago>UI to reverse the list order or jump ahead But why would you ever want to do that? The system already picks the best videos for you to watch, so you wouldn't even have to scroll.
- jazoom 8y agoI'm also Australian and didn't realise it was because of this. Actually, I'm still skeptical this is the main reason since it's like a 260ms round trip to East coast USA. Let's say the latency for someone not living on our big old island is 80ms round trip. I don't think the extra 180ms will make that big of a difference if the app is well designed. That's still enough time to detect scrolling and have the new data ready by the time the user turns the mouse wheel twice. I should add that I've always suspected a lot of developers don't test their apps with latency in mind, so they make silly decisions like serial requests, etc. They never see how awful the experience is for someone not living next door to their data centre.