Conventional display "page of page" (7 of 23), range of total. This one is the interactive version. You can click prev/next, to a range, to a page, etc. All options covered... ALSO try to integrate gesture (or key) flip as for eReader style. Fake page flips, as indicator there are more pages (show accurate stack of pages, so it works like a scrollbar for position sense) and to indicate you moved to a new page.

Problem

Location within a series of screens continuing display of a set of content should be clearly communicated, and access provided to other pages in the stack.

Solution

The many screens displayed serially for large amounts of content may be considered pages, as though they are part of a bound paper item.

Page numbers, and a sense of the relative position within the total, are displayed.

Tied to this display is a method to move between pages easily and quickly. Methods to jump further than the previous and next page are also usually offered.

When building a system with large amounts of information consider if a multi-page view is even correct. In many cases, Infinite List can solve the same display problem without building a pagination widget at all.

Consider other methods of discovering information in large sets, such as the Search Within pattern.

Variations

Two basic variations exist:

Widget-based - A section of the page is dedicated to the display and control of items concerning pagination. Very often, there are actually two of these, with the same or a similar widget repeating at the top and bottom. If not, the item must usually be anchored to a non-scrolling title bar, so it is always accessible.

Organic - Natural displays are becoming more common now, especially on touch and pen devices. These simulate "machine-era" presentation methods to imply the same information as the widget view. The display methods and interaction is integral with the design of the entire page, and is not in a specific location.

Interaction Details

Pagination controls should be presented organically, with all controls visible or immediately accessible, whenever possible. When needed, a larger control panel style of interface may be offered instead. It may be accessed by selecting the pagination display elements.

A number of controls are available. Many are paired sets, and will be considered as a single entity. There are a large number, which must be prioritized for display and access. The following are listed in priority order for most uses, though yours may vary:

For each of these, only display pages that actually exist. Gray out those which are not accessible due to current context. For example "Back" or "First page" links should be visible but inaccessible when already on the first page.

The forward and back control may be easily activated on touch and pen devices, either by tapping an indicated corner of the page (right is next, left is previous) or by gesturally "flipping" the pages, with a drag action. Details on a related drag action may be found in the Peel Away pattern.

Some of the more involved jump methods may also be initiated or carried out with gestures, and actions such as press-and-hold on the page flip section. However, these are not yet consistent and well-defined, so cannot yet be considered patterns.

Presentation Details

clicky ones...

arrows and labels... use play controls, such as arrow for next, arrow with vertical line for jump or jump-to-end... note these are not universal and the "chapter skip" icon for playback has no distinct, universal meaning here so will have to be learned...

Gestural ones.... and especially the implication of page thickness...

Antipatterns

Pagination controls can easily get out of hand. In any reasonably complex system, it is easy to find justification for every method of page control. Avoid this, and attempt to only include the minimum set needed, so they can be placed on the page and be easy to find and use.

Realist representations of pages must accurately reflect the information. For example, if a stack of pages is shown to the side, to indicate that more are available, the relative number shown must be of a plausible size to represent the number of pages, and must change the indicated size as pages are flipped.

Avoid cumbersome entry or methods. For example, do not present pulldown lists of pages that are longer than about a dozen items, even on large screen devices. Offer typed entry, or some entirely other solution instead.

Examples