ux-research checked
Nielsen Norman Group: Infinite Scrolling: When to Use It, When to Avoid It
Explains infinite scrolling as continuous content loading and covers when it supports browsing versus when pagination or load-more controls better preserve orientation and task completion.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Feed | Choose feed when the core experience is consuming a continuing stream rather than managing a fixed set of objects. | Each feed item has a stable identity, source, timestamp, item boundary, and primary destination or action. | NN/g supports orientation and loading rules for feeds that use continuous scrolling or load-more behavior. |
| Infinite scroll with no footer access | Flag this anti-pattern when automatic loading prevents reliable access to footer links, page end, support routes, legal links, feedback, or other bottom-of-page utilities. | Users can reach footer utilities without racing automatic loading. | Supports distinguishing infinite scroll, load-more, and pagination by orientation, task completion, and footer reachability risks. |
| Pagination without current page | Flag this anti-pattern when a pagination set has no visible current page, no aria-current or equivalent current-state text, or more than one item that appears current. | Each pagination region has one owner collection and one current page or current range. | Supports distinguishing continuous feeds from pagination when users need orientation, position, or task completion. |
Evidence Role
This source is treated as ux-research evidence. Use it to validate the decision rules above, not as a visual style reference.
Publisher: Nielsen Norman Group. Last checked: .