Skip to content
Astera Technology

Page navigation or load more for a work queue?

Choose a browsing method that preserves position and selection when staff return from a detail record.

Choose against the task constraints

A synthetic team reviews a queue of 93 records ordered by creation time and ID. Page size is twenty. A reviewer opens a record, returns and continues from the same location. New work may arrive during review, so the design also needs a stable sorting or snapshot rule.

Decision worksheet
ConditionPage navigationLoad more
Return to a known positionPage/filter state can identify a bounded sliceRestore loaded extent and scroll position
Continuous scanningRequires explicit page changesCan append the next bounded slice
Large result setKeeps each rendered page boundedRepeated appends need a DOM/retention strategy
Download editable CSV ↓

Use explicit pages for this review queue unless load-more restoration is implemented and tested. Neither control fixes unstable sorting by itself. Keep the filter, unique record identity and order consistent across the return journey.

Identify the final slice

Synthetic task cases
PagePositionsRecords
11–2020
461–8020
581–9313
Download editable CSV ↓

How many pages exist, and is page five a full twenty records?

Show the worked answer

Five pages. Four full pages contain eighty records, leaving thirteen on page five. An empty next page must not be advertised as available.

Check the chosen interaction

  • Opening and returning from a detail retains the intended queue position.
  • A new arrival does not duplicate an already reviewed identity within the declared snapshot.
  • The last slice disables or omits a nonexistent next action.

Related resources