Interface Lab
Back to knowledge
Interaction Responsive Motion

Infinite Scroll vs Pagination

Infinite Scroll vs Pagination turns a frequent interface judgment into an executable constraint before generation.

Design Principle

Browse lists can scroll continuously; task lists usually need position, selection, return, and count awareness.

Principle

Browse lists can scroll continuously; task lists usually need position, selection, return, and count awareness.

Design action

Use infinite scroll for discovery; prefer pagination or load-more for admin, search, orders, and review lists, preserving position.

Examples

Positive example: A list must choose between discovery browsing and precise management. Counterexample: An admin table uses infinite scroll and loses selected position.

Apply when

A list must choose between discovery browsing and precise management. Users need to judge state, scope, risk, or next action quickly.

Source notes

Source note: Synthesized from Apple HIG, Material Design, GOV.UK/Polaris/Atlassian component practices, and interaction accessibility principles. Apple HIG Motion: https://developer.apple.com/design/human-interface-guidelines/motion Material Design Motion: https://m3.material.io/styles/motion/overview/how-it-works GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Shopify Polaris Patterns: https://polaris-react.shopify.com/patterns Atlassian Empty State: https://atlassian.design/components/empty-state

Agent Directive

Use infinite scroll for discovery; prefer pagination or load-more for admin, search, orders, and review lists, preserving position.