The permanent menu - with locator options - at the bottom is brilliant.
Google’s suggestion for a better infinite scroll?
11–20 of 168 posts
Re: Google’s suggestion for a better infinite scroll?
#12Love this. If only Hacker News and Reddit would implement it.
... and Google.
Re: Google’s suggestion for a better infinite scroll?
#13Favor: could someone share an intelligent (or at least in-depth) write-up of the pros/cons of infinite scrolling? Most of what I'm finding on the web is content farmy. Also: at what point is memory usage worth worrying about? Scrolling for pages on end has to be tough on a browser.
Here's a good piece about why it didn't work at Etsy: http://danwin.com/2013/01/infinite-scroll-fail-etsy/
A presentation that goes into some of these results is here: http://mcfunley.com/design-for-continuous-experimentation
Re: Google’s suggestion for a better infinite scroll?
#14Favor: could someone share an intelligent (or at least in-depth) write-up of the pros/cons of infinite scrolling? Most of what I'm finding on the web is content farmy. Also: at what point is memory usage worth worrying about? Scrolling for pages on end has to be tough on a browser.
pro : good for mobile users -
con : no footer
Re: Google’s suggestion for a better infinite scroll?
#15I suggest not using infinite scrolling. It's annoying as hell when I want to get back to where I was or just browse some older entries.
Re: Google’s suggestion for a better infinite scroll?
#16It still jumps around if you hold and drag the scrollbar - always my complaint with these.
I wonder how many people do hold and drag the scrollbar, I am so used to scrolling using a touchpad on Mac and mousewheel on PC, so I never even touch a scrollbar.
Re: Google’s suggestion for a better infinite scroll?
#17Love this. If only Hacker News and Reddit would implement it.
Please do not implement infinite scroll. I find it super annoying.
Re: Google’s suggestion for a better infinite scroll?
#18Doesn't this still effectively break the back button or at least the users view of the back button? To the user although there are visual hints, he/she hasn't left the page. Scrolling down the page however creates multiple history entries.
Re: Google’s suggestion for a better infinite scroll?
#19This also needs to keep only N pagefuls above and below the page cut. E.g. if N is 2 and I'm on page 5, then it would only have pages 3-4,5,6-7 in DOM.
This would ensure that users get the same scrollbar range on page 5 regardless of whether they infi-scrolled themselves there or just clicked on "page 5" in the index.
Re: Google’s suggestion for a better infinite scroll?
#20It still jumps around if you hold and drag the scrollbar - always my complaint with these.
I tend to dislike pure infinite scrolling and instead prefer on-demand loading.
With on-demand loading you would set the virtual height of the scrollable area to the height necessary to show all (or a huge chunk of) your data, and then page in chunks of the data as it approaches the viewport.
Then dragging the scrollbar works, and touch scrolling shows a reasonable representation of how much data is left.