Imagine having a book where no matter how much you read, it never seems to end. No milestones, no sense of progress. Just page after page after page.
It just feels... icky.
Imagine having a book where no matter how much you read, it never seems to end. No milestones, no sense of progress. Just page after page after page.
It just feels... icky.
To paraphrase Jeff Goldblum's "Ian Malcolm" in Jurassic Park:
"Yeah, but your front-end developers were so preoccupied with whether they could that they didn't stop to think if they should."
I personally find infinite scroll to be far worse than cleanly paginated pages in every regard. YMMV, I guess.
I don't hate infinite scrolling as much as I used to, but I think that's just because I'm not a heavy user of any sites that have infinite scrolling.
Meanwhile all the stuff you have already read is sitting around in a big mess, doing nothing but taking up space and getting in the way.
Infinite scroll encourages users to keep going. It's similar to how certain demographics will scroll through Pinterest for hours. It removes the boundary where someone might say "OK, that's the last page I'm going through."
OTOH, there are many, many ways to mess up pagination UI as well. Not showing how many pages there are is one that often annoys me, because one time I will go through a bunch of pages of stuff is if I am quickly visually scanning to find something I saw before but couldn't track down with search or bookmarks all that quickly for some reason. If I know what I am looking for is on one of 15 pages then there is a good chance I can find it quickly, but with 50 pages it might be more effective to keep trying my luck at search (or just give up).
The addendum to Fitt's Law is key here: The current location of the pointer is an infinite target.
Or, to paraphrase, dragging is usability hell.*
If I'm flipping through pages, I want to click or tap one thing, I don't want to have to manipulate things by clicking one spot, holding a button, finding another target and releasing.
I know clicking and dragging is intuitive and easy for all of us, but compared to one simple click at the current mouse location, it's a usability eternity.
My approach would be to display all search results from the first page of Google cleanly on one screen. Maybe two columns wide if necessary, or fit to the screen in a tumblr style way. Not infinite scrolling, not any scrolling. I can keep my mouse on top of a little set of forward and back arrow buttons in the corner and flip through results that way. Or I could just use arrow keys or taps on a mobile device.
* Sure, dragging is the only sensible approach in some cases, maps and canvases and 3D object manipulation, sure. But if it can be designed away.
So I could see click and drag if your search results were not linear, but a two dimensional graph. Maybe you get that graph by... going right or left puts more priority on different terms in the search box, or going up and down adds different commonly included words to your search, I don't know.
The mobile browser performance is still much lower than on the desktop, so you don't want to render too large a DOM at once.
Loading a new page over the network can easily take 10s, if you need to reactivate the 3G connection from a low-power state. Of course you can use a single-page-app approach to help that bit.
Scrolling in one direction is one of the easiest (and most fun) interactions you can do on a touch screen - clicking is much harder.