Removing natural stopping points
Aliases: stopping cues · feed boundaries · structural breaks
What it is
The bottom of a page, the end of a list, a "no more items" notice — these are the interface's natural stopping points: occasions on which the question "keep going?" actually gets asked. Infinite scroll removes every such boundary, making continuation the default that requires no decision.
Why it happens
A stopping point manufactures a decision moment. In a bounded list the user must perform a small act to continue at each boundary, and that act happens to carry a lightweight evaluation of whether continuing is worth it — not deliberate, but present. Remove the boundaries and "continue" stops being a chosen action and becomes the default of doing nothing; "stop" now requires initiative: noticing that one is scrolling, deciding to end, executing the exit. Default effects amplify the asymmetry: staying with the default is nearly free while leaving it demands first noticing the default exists. Continuous content supply also refills whatever satisfaction is consumed, so any internal "that's enough" signal finds no external structure to land on.
Where it stops holding
The value of stopping points depends on content and task. In browsing and leisure contexts users need no boundaries, and forced pagination is pure friction; in retrieval and tool contexts boundaries are part of the task structure and removing them is a net loss. Stopping points can also be too dense — a break every screen shatters browsing coherence and errs in the opposite direction. This entry answers only whether to provide structural boundaries; the mechanisms of pull-to-refresh and autoplay are separate questions.
Applying it
Keep pagination or an explicit "all loaded" terminal state in every list outside the leisure feed (search results, orders, settings). Where infinite scroll is justified, provide substitute structural pauses to catch stops: section headers, time separators, an end-of-today marker. The terminal state must be genuine — nothing may load after "no more," or the stopping point is learned to be a lie and stops working. Verification: in a usability test, let users browse naturally and watch how they signal "enough" — reports of difficulty self-interrupting, or long aimless scrolling that never terminates, indicate the structure has nowhere for stopping to land.