Improving on Infinite Scrolling
- February, 24, 2008
- 4 Comments
I’ve been thinking a lot about infinite scrolling lately. We’re cooking up some interesting stuff and Viewzi and are considering implementing this behavior in a few very specific scenarios.
What is infinite scrolling? Instead of breaking content into ‘pages’, as a user nears (or scrolls to) the end of a set of content or results, more content is seamlessly loaded behind it creating one long continuous page. Humanized likes this approach because the concept of “pages” really has no semantic meaning to a person. Those numbers at the bottom of the page don’t really mean much. Second, and perhaps most important, by scrolling to the bottom of a “page” the user is essentially telling the system that they are ready for more content. Why should they have to ask for it?
A few years ago, Matt from 37 signals pointed out that infinite scrolling turns your scrollbar “into a liar” because the “bottom” of the page actually becomes the middle once new content is loaded.
The dancing scrollbar has no effect whatsoever when scrolling with the keyboard or mouse wheel. You can scroll uninterrupted using either mechanism. But to Matt’s point the concept of top, bottom, or middle is broken with infinite scrolling. Take away the concept of “pages” and you could have a problem. Why? What if you scroll through a ton of content and need to go back to something you past. Finding it could be tricky without some way to mentally bookmark where you saw it. Infinite scrolling works fantastic for scrolling “through” content, but falls flat when you need to go back to something.
I’m not convinced that the lack of semantic meaning behind pagination is a problem, but not having to ask for more content is really, really powerful. Can’t we combine both? Reading through the comments I came across a surprise from commenter Nate:
Why couldn’t there be a floating status widget in the corner of the screen giving you a relative idea of where you are?
You could designate that 10 items equals one page, (Page 5) or just show how many items from the top you are (#50).
Note: I would be careful with how I use the word “page” since it’s all really one page.
Nate has a brilliant idea. Is solving this problem really as simple as adding visual way points so users can get back?
Now that you know where the piece of information is that you are looking for, how do you get there? With pagination, each page is the same “distance” from each other. With infinite scrolling, each “page” you scroll through potentially puts you further and further away from the result you actually wanted.
By providing a simple “running” pagination that grows as you scroll you provide users with direct access back to any section. This is essentially what the scroll bar does (that infinite scrolling breaks) but is much more accurate.
Natalie Jost said:
Hey, I’m new here. Just saying hello, and I love this concept… looking forward to reading more about it as it develops. All very good points you’ve made and helped me understand (since I can’t see it in action) what it would do/be.
Thanks for stopping buy Natalie! Stay tuned (an nice site BTW!)
The Interaction Design Pattern @ Infinite Scroll said:
[...] Consider a faux pagination widget to allow for navigation within the new content. Travis Isaacs has ideas on a running pagination. [...]
That’s an incredibly deep idea…I can’t wait to see you/someone pick it up and run with it. I wonder how resource heavy it would be…I hope you can code this soon cos I’m in the process of coding a new site so I’m all for trying out new ideas!!