Infinite scroll conflicts with retrieval tasks

What it is

Retrieval tasks — finding a specific item, comparing options, checking a record — end at "found, or confirmed absent"; infinite scroll has no end and reports no remainder. Combined, the task loses its judgment structure: the user can never know whether they are approaching the target or whether the target is not in the stream at all.

Why it happens

Rational search needs two pieces of information to sustain itself: the remaining amount (how much is unseen) and coverage (whether the seen portion could contain the target). The infinite feed offers neither — continuous generation means "not found" may always be merely "not yet seen" and can never be upgraded to "absent," so stopping the search has no defensible basis and continuing is the only justifiable act. The interface simultaneously cancels the completion signal (last page, result count), refusing to recognize the task's terminal state. It is a structural mismatch: a browsing container — goalless, ending in depletion — loaded with a retrieval goal — bounded, ending in finding.

Where it stops holding

Not all search suffers. Retrieval interfaces with a query box, sorting, and result counts preserve the judgment structure; the conflict belongs to those that infinitize search results. In-page find (finite match counts) partially restores judgment — a common user workaround. For fuzzy retrieval — browsing for inspiration with no specific target — unbounded supply fits, and no conflict exists. The deciding question is whether the task has a "done" the user can recognize.

Applying it

Do not infinitize search results: keep result counts, pagination, or explicit scope statements ("N results, sorted by relevance"). Where mobile scrolling is necessary, provide an indication of the searched range and an entry to tighten filters, so "narrow the scope" replaces "keep scrolling" as the next move. Separate browsing feeds from search results in interaction and visuals — users should recognize at a glance which container they are in. Verification: compare task completion and time-to-confirm-absence between presentations — the time to confirm an empty result is the sensitive indicator; under infinite feeds it tends to infinity (users abandon confirmation rather than complete it).

Related

• Same group: P3.08.1 Infinite scroll strips content of addressable positions · 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
• Adjacent: G4 Information finding and search · P3.02 Infinite scroll
• Search terms: retrieval task · search termination · information seeking · infinite scroll