The Internet Sucks
Infinite scroll removed the bottom of the page on purpose
The end of a list used to be a natural place to stop. Somebody noticed that stopping points cost engagement, and deleted them.

The theory of infinite scroll is well covered elsewhere. This is about the version you meet in practice.
What holds up in practice
- Pagination provided a stopping cue that infinite scroll deliberately removes.
- Variable reward scheduling makes unpredictable feeds harder to leave.
- Reduced navigability is a documented usability cost of endless feeds.
Stopping cues used to be built in
A paginated list ends, and the act of clicking to the next page is a small decision that gives a person a chance to stop. Infinite scroll removes that decision by loading the next batch before you reach the end, so no boundary is ever presented.
The design is defended on smoothness, and it genuinely is smoother, in the sense that a road with no junctions is smoother. What disappears alongside the friction is the moment of noticing how long you have been doing this. Interface researchers described the loss of stopping cues long before the pattern became universal, and the pattern became universal anyway.
Unpredictable rewards are harder to leave
A feed mixing occasional genuinely interesting items into a stream of ordinary ones follows a variable reward schedule, which is well studied and reliably compelling. The next item might be the good one, and because the interval between good ones is irregular, no natural point to quit ever arrives. Ranking systems optimise for exactly this by placing engaging content unpredictably rather than in a predictable block.
On hold for the fourth time, the effect is not a moral failing on the part of the reader, it is a property of the schedule rather than of the person. Understanding that helps mainly by removing the guilt, which is otherwise a large part of why people stay scrolling.
The usability costs are real and boring
Endless feeds break the browser back button, because returning to a page reloads it from the top and loses your position entirely. They make it difficult to reach anything below the feed, which is why site footers on scrolling pages became functionally unreachable. Finding a specific item again is close to impossible without a search function, since the position of anything depends on when you looked.
Screen readers and keyboard navigation cope poorly with content that appends continuously beneath the current focus. These are the ordinary reasons interface designers disliked the pattern, entirely separate from the attention argument.
Pull to refresh is the companion mechanism
Pull to refresh adds a physical gesture that produces an unpredictable outcome, which is a fairly exact description of a lever on a machine. Feeds that could update automatically frequently do not, because the gesture is more engaging than a silent update would be. The animation is tuned to feel satisfying, with resistance and a release, which is deliberate interaction design rather than a happy accident.
Three clicks later, combined with endless scroll, the result is a surface with no end and a manual control for generating more of it.
It is genuinely elegant work, in the way a very good trap is elegant work.
Where infinite scroll is fine
For browsing with no goal, such as images or a map, continuous loading suits the task and the criticism largely does not apply. For search results, product listings or anything you might need to return to, pagination is simply better and most retailers know it. The distinction is whether the user has a target, because a target makes position, retrievability and completion matter.
The bit they bury in the confirmation email: sites that use infinite scroll on results while offering a page counter are hedging, and the counter is the part that helps. Judging the pattern by the task rather than by the aesthetics gets you to the right answer almost every time.
Practices change, and a company that does this today may have quietly stopped by the time you read it.
Rebuilding the bottom of the page
Many apps offer a chronological or following-only feed, which is finite by definition and ends when you have seen everything. Browser extensions that replace endless feeds with a fixed number of items restore a stopping point on the desktop.
On hold for the fourth time, removing the app and using the mobile website works because mobile sites are usually worse, which for once is the desired outcome. Setting a timer is weaker than removing the mechanism, because willpower is being asked to compete with a tested system. The most effective changes are all structural rather than motivational, which is the same conclusion as almost every other article in this section.
The takeaway
Choose the chronological feed, because it is the one with an end.
It is not you being fussy. It is genuinely badly made.
Questions readers ask
Is infinite scroll always bad design?
No. For open-ended browsing it fits the task. For anything with a goal, pagination preserves position, retrievability and a sense of completion.
Why does the back button lose my place?
The feed is assembled by script after the page loads, so returning rebuilds it from the top unless the site deliberately saves state.
Also by Kartik Sahoo
- Reject All is one click, unless somebody paid for it to be twelveThe Internet Sucks
- Why the recipe sits at the bottom of a short memoirThe Internet Sucks
- Only three left, apparently, for the last six monthsThe Internet Sucks
- To stop receiving these emails, please remember a password you never setThe Internet Sucks





