Paginator
Overview
Use pagination when records are sorted in a logical way (ie, chronologically or alphabetically). Pagination allows users to mentally bookmark or orient where they are in an ordered result set. Pagination can be used with collections: tables, lists, and cards.
Infinite scroll vs pagination
Infinite scroll is best used to encourage discovery or exploration when users are casually browsing content. Infinite scroll may also be a better option for mobile contexts. By contrast, pagination is best used for datasets that have been sorted in a logical way, as it allows users to jump to a specific page or mentally orient where they are in a set.
Best practices
Allow users to set how many records they want to display per page.
If loading time is a consideration for larger data sets, consider using a default with fewer records per page and allowing users to choose how many records per page.
When a user navigates back from a detail page within a record set, return them to their previous spot in the collection, even if it wasn't on the first page.
Don't use fixed positioning on a paginator - it should be displayed below the visible list.
The paginator should not cover content on the page.
Related
Components
A paginator may be used with: