All these problems are solvable. I co-founded Discourse ( http://discourse.org ) which uses infinite scrolling heavily. Discourse is also 100% open source so you can see how we did it. My responses below: > Users will lose the page length orientation - the browser scrollbar become useless. We have a fixed "x/y" posts widget at the bottom with a progress bar. > There’s no ability to jump to the end of the list. The af…
Your response is excellent. But something is missing here, an awareness of when infinite scrolling is good vs bad. Infinite scrolling is good when the information is ephemeral, and changing all the time. Dating profiles, twitter stream, live updates. But infinite scrolling is bad when the content is fixed. Like a forum. There is a cognitive clue when paging through a forum, how far you have read, where you are. All y…
"post x/y" tells you how far you are in the page, but only if you think about it. There's no longer any intuitive connection between the scroll bar and page position. The End key stops working intuitively, sends you to the end of currently loaded posts and then loads more posts so 1 second after pressing it you're not at the end of anything. Then there's the lag as you hit the top or bottom of currently loaded posts; even if you don't want to read any more, you get more. That's clever if you're a tabloid magazine because it entices the reader to read more, but the impression I get is it's not productive.
For maximum usability, why shouldn't the app support both infinite scroll and paginated, and let the USER choose (by url slug or GET param)? (Or by user setting if logged in)