Pagination supplies location and revisability
Aliases: addressable pages · page coordinates
What it is
Pagination cuts a long result into numbered chunks, each with a place that can be spoken and written into an address: page k of n. Location is “which stretch of the whole set am I in”. Revisability is “I can open that same stretch again”. It is not about how many rows to show at once, and not about how to leap to page 87. It is that the result space has been cut into addressable places.
Why it happens
Estimating how much remains, whether to continue, and how to hand a result to someone else or to tomorrow’s self, all depend on a stable coordinate. Page numbers give two: an ordinal (page 4) and a bound (of 40). The ordinal makes “that screen just now” into an object — save, share, and compare have a name. The bound creates an expectation of ending, so a search can stop after some pages without suspecting an infinite remainder. The address bar, a query parameter, or the page control externalises the coordinate, so refresh, Back, and another device can still land on the same chunk.
A numberless continuous stream can still scroll, but “that stretch” cannot be named. People hunt with a blurry memory (“I scrolled for a long time”), and collaboration and cross-session work break. Pagination spends a cut in continuous scanning and buys a place that can be pointed at. If the numbers are decoration and the actual address does not change with the page, location is fake: refresh jumps to page one, and “page 4” cannot be cited.
Studying it
Use a revisit task: have someone mark a target in the results, leave, and return to the same item from memory or notes. Independent variable: page coordinates versus a continuous stream. Dependent variables: steps to revisit, landing on the wrong chunk, and whether place can be spoken (“middle of page three” versus “I scrolled a lot”).
End estimation can be measured separately: ask “about how much is left”. With “n pages” the estimate converges; with endless append it diverges or people refuse to answer. That measures location, not whether a loading style is pleasant.
Where it stops holding
When the set is small enough to exhaust in one page, pagination chrome is noise and “already at the end” carries location. On a timeline that mutates hard in real time, page coordinates stale quickly — tomorrow’s page 3 is not the same objects — and revisability holds only inside a short window. Personalised ranking differs per person: a page number can locate inside one session and still fail as a shared address. Print, export, or an accessible “jump to item n” is sometimes a better coordinate than pages. Endless generated content has no natural whole set; pagination then fakes a bound that does not exist.
Applying it
- Give every page a stable coordinate in the address (query or path). Refresh and share should land on that page, not merely paint a highlighted numeral on the control.
- Show current page and total together (or “about n pages” when the total is an estimate) so the end can be perceived.
- After a page change, put focus and scroll at the start of the results and keep the filters, so the coordinate does not change while the world looks swapped.
- How to check: open page n, paste the address into a new session, and the chunk should match. Ask someone a few minutes later to recover the earlier item by page number; failure means no coordinate was built. If they cannot answer “how much is left”, the bound was not expressed.