Infinite scroll strips content of addressable positions

What it is

An infinitely scrolling list has no "page 3, item 7": content in the stream has only relative order, no restatable, revisitable position. Addressability — "where is it" having a stable answer — is what pagination and bounded lists provide and what the infinite feed revokes.

Why it happens

Position memory relies on spatial anchors: page numbers, screen ordinals, scrollbar proportions give recall a coordinate system to hang on. In an infinite feed the coordinate system itself drifts with loading: return to the top and scroll down again, and the arrangement has changed — new items inserted, entries reshuffled — the old position is void, so "where I left off" is unreliable. Users either rescan (search cost eating browsing's payoff) or outsource positioning wholesale to the system's memory (read markers, history). Non-addressability also reshapes processing: since revisiting is hopeless, close reading is a poor investment, and scanning degenerates into skimming — unstable positions not only make content unrecoverable, they shallow the processing happening now.

Where it stops holding

Addressability matters for revisiting use: disposable leisure streams (short-video chains) barely need position, consumed and abandoned; tool lists (orders, email search results) depend on it exactly, and infinitizing them is a net loss. System-level compensation — history, read-later, read lines — restores positioning partly, but depends on active use and hides in deep menus. The root of instability is insertion-style updates (new content pushing between old); append-only chronological feeds are comparatively stable, and the problem is much lighter.

Applying it

Keep addresses for lists that get revisited: pagination, anchor links, shareable permalinks to single items. Give feeds an explicit session breakpoint ("continue from here" auto-bookmark) with the entry visible in the stream, not buried in a menu. Put sorting strategy's effect on addressability into design review: insert-and-reshuffle versus append costs revisit differently — choose explicitly rather than accept the default. Verification: measure time and failure rate for "resume where you left off" tasks, infinite feed versus paginated — the recovery cost quantifies the loss of position memory.

Related

• Same group: P3.08.2 The decision cost of continuing to scroll is reduced to zero · P3.08.3 The page-turn of pagination is a natural exit opportunity · P3.08.4 Infinite scroll conflicts with retrieval tasks
• Adjacent: P3.02 Infinite scroll · G4 Information finding and search
• Search terms: addressability · infinite scroll · position memory