I've thought about and implemented this a number of times, and I've noticed along the way that the hate against infinite scrolling often boils down to "I just w

I've thought about and implemented this a number of times, and I've noticed along the way that the hate against infinite scrolling often boils down to "I just want to do things the way I've always done them, get off my lawn", or "this particular boneheaded implementation of infinite scrolling will be the case I use to damn the entire concept" - Infinite scrolling is best used for browsing content, especially ephemeral content. It's an anti-pattern for content that needs to be managed in a granular way. - A common argument is "I want to save this link" and return to it at a later time. Unfortunately, unless you're looking at completely static content, even e-commerce inventories change over time and page 10 isn't going to be the same content the next time you return. This is what detail views are for. - Memory bloat is commonly cited, and yes, it's painful to implement a good scrollview, but at the same time, it's pretty much a solved problem at this point. The Mashables of the world are just too lazy to fix it. There are a number of active open-source widgets that will solve this for you. Well-thought out libraries like Angular's Ionic will deal with this transparently. - The old "disappearing footer" is, IMO, a "dark pattern", and one that just happens to be empowered by infinite scroll. It's a business decision to make it difficult for you to get to that footer. It would take about 10 minutes of CSS to solve that problem. I'll admit that for conversion/sales focused browsing, it's an anti-pattern. When new content keeps popping up, people are more likely to continue browsing than jump into a detail view and make a purchase. For newsfeed browsing, the hate is, for the most part, misguided.