Pagination is the row of controls at the foot of a long set that says which slice is on screen and moves the reader to another one. It is the cheapest way to make a position nameable: a page can be linked, bookmarked, reloaded and read aloud to a colleague, none of which is true of a scroll position. Paired with a count, it also tells the reader how big the set actually is before they commit to working through it.
Most of the design is in what the row refuses to do. The window of page numbers holds a fixed set of slots, so it never changes width as the reader moves and the button under the pointer never walks away. The ellipsis is a gap and not a control: no border, no hover, nothing behind it. Arrows at the ends fade rather than vanish, for the same reason. And how many rows a page holds is half the feature, usually bolted on last.
Under a record table, next to a rows-per-page control and a count. The count is what turns an abstract row of numbers into a set with a known size, rather than a next button that might go on forever.
Result lists where relevance falls off with depth. Nearly all the traffic sits on the first page, so reaching the previous page and seeing an honest total matter more than a jump to the end.
Screens where one person works through records over days and has to resume where they stopped. A page number kept in the address survives a reload and a shared link; a scroll position survives neither.
Sets too large to fetch at once, where a page is the request itself. How many rows a page holds is part of that request, which is why the choice belongs beside the pager rather than in a settings menu.
Enough to reach the first page, the last page and the neighbours of the current one, and always the same number of them. A window that grows and shrinks as the reader moves makes buttons wander under the pointer. When the whole set fits inside that window, draw every page: an ellipsis standing in for a single page hides nothing and costs a click.
They answer different questions. Pagination produces a position that can be linked, reloaded and returned to, keeps the footer reachable, and suits sets people search rather than browse. Infinite scrolling suits feeds read in order with no destination. A set that changes while it is being read is served badly by both, and a cursor anchored to the last record seen stops items shifting between pages.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Pagination is the row of controls at the foot of a long set that says which slice is on screen and moves the reader to another one. It is the cheapest way to make a position nameable: a page can be linked, bookmarked, reloaded and read aloud to a colleague, none of which is true of a scroll position. Paired with a count, it also tells the reader how big the set actually is before they commit to working through it.
Most of the design is in what the row refuses to do. The window of page numbers holds a fixed set of slots, so it never changes width as the reader moves and the button under the pointer never walks away. The ellipsis is a gap and not a control: no border, no hover, nothing behind it. Arrows at the ends fade rather than vanish, for the same reason. And how many rows a page holds is half the feature, usually bolted on last.
Under a record table, next to a rows-per-page control and a count. The count is what turns an abstract row of numbers into a set with a known size, rather than a next button that might go on forever.
Result lists where relevance falls off with depth. Nearly all the traffic sits on the first page, so reaching the previous page and seeing an honest total matter more than a jump to the end.
Screens where one person works through records over days and has to resume where they stopped. A page number kept in the address survives a reload and a shared link; a scroll position survives neither.
Sets too large to fetch at once, where a page is the request itself. How many rows a page holds is part of that request, which is why the choice belongs beside the pager rather than in a settings menu.
Enough to reach the first page, the last page and the neighbours of the current one, and always the same number of them. A window that grows and shrinks as the reader moves makes buttons wander under the pointer. When the whole set fits inside that window, draw every page: an ellipsis standing in for a single page hides nothing and costs a click.
They answer different questions. Pagination produces a position that can be linked, reloaded and returned to, keeps the footer reachable, and suits sets people search rather than browse. Infinite scrolling suits feeds read in order with no destination. A set that changes while it is being read is served badly by both, and a cursor anchored to the last record seen stops items shifting between pages.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Page 10 of 20·181–200 of 388 orders
1–20 of 512 invoices
Page 1 of 13·1–20 of 248
Jump toPage 10 of 20·181–200 of 388 orders
1–20 of 512 invoices
Page 1 of 13·1–20 of 248
Jump to