Infinite scroll was not an inevitable evolution of the web. It was a deliberate design choice.
Before it became the default, most digital content lived on pages. You finished a page, you clicked “next,” and the act of clicking created a small moment of decision. That moment was friction. Friction, in the attention economy, is a cost.
Removing it was the point.
How the Feature Works
Infinite scroll replaces a discrete unit of content (the page) with a continuous stream. As you approach the bottom of what is currently loaded, more content appears automatically. There is no clear endpoint, no natural pause, and no requirement to make an active choice to continue.
The technical implementation is straightforward. The psychological effect is not.
A page has boundaries. When you reach the end, the brain registers completion. Infinite scroll removes that signal. The feed never finishes; it only pauses briefly while the next batch loads. The absence of an ending keeps the consumption loop open.
Designers understood this. Product teams measured it. Time-on-site and session length usually increased when infinite scroll replaced pagination. That increase was treated as success.
The Trade-Off That Was Accepted
Pagination asks the user to decide whether the next page is worth the click. Infinite scroll removes the decision. The default becomes continuation.
This is efficient if the goal is to maximize exposure to content and advertising. It is less efficient if the goal is to help someone find what they came for and leave. Most consumer products optimized for the first goal.
I sat in meetings where we discussed the metrics. Longer sessions were framed as higher engagement. Higher engagement was framed as a better product. The fact that people were spending more time without a clear purpose was rarely examined as a potential downside. It was simply the number going in the desired direction.
What Changes When You Notice It
Once you start seeing infinite scroll as a designed absence of stopping points, the experience shifts.
You notice how rarely a feed feels finished.
You notice the slight hesitation when the loading spinner appears, and how quickly it resolves into more content.
You notice that “just a little more” has no natural limit.
The feature is not broken. It is working exactly as intended. The intention was never to help you stop.
A Small Way to Reintroduce Friction
You cannot remove infinite scroll from most of the apps you use. You can change how you interact with it.
One practical approach: decide in advance how much time or how many items you will give a feed. When you reach that limit, close the app instead of waiting for the next automatic load. The decision moves from the interface back to you.
Another approach: prefer interfaces that still use pagination or clear “load more” buttons when they exist. The extra click is not a flaw. It is a reminder that continuing is optional.
Neither method is dramatic. Both restore a small amount of the agency that infinite scroll was designed to reduce.
The Larger Pattern
Infinite scroll belongs to a family of design decisions that remove natural stopping points: autoplay, endless recommendations, notifications that arrive without being requested. Each one makes the next action slightly easier than stopping.
None of them are accidents. They are the result of clear priorities. Those priorities were usually measured in engagement time, not in whether the time felt useful to the person spending it.
You need less than you think. Sometimes the most effective feature is the one that never lets you feel finished.
