The actor is working through a collection item by item — scanning many candidates, checking ones of interest — and no single view serves both motions: none is at once compact enough to scan and rich enough to verify.

Forces

• Scanning vs. verifying — showing everything at full fidelity overwhelms; one item at a time loses orientation and comparison
• Compactness vs. answering in place — the fewer attributes the overview carries, the more questions can only be answered inside items, forcing pogo-sticking: the roundtrip into each item just to answer a scanning question
• Preference vs. performance — users consistently prefer having an overview even where it doesn’t improve performance, so the overview claims screen space its measured benefit may not justify

Solution

Give the collection two linked views: an overview rendering every item in the same compressed form, and a detail view rendering the current item in full. The link is the current item: opening an item from the overview fills the detail view, and returning to the overview finds the actor’s place kept. Whether the two views share the screen, swap in place, or sit on separate pages is a layout decision inside the pattern, not the pattern itself.

Dimensions

Content

Which attributes live in which view: overview only, detail only, or both — and interactive elements count as attributes too (a save button can live in both views or only one). The overview’s subset is the consequential choice: it fixes what the actor can compare, sort, and filter by. Held open to the actor rather than fixed per view, this dimension is attribute visibility applied twice over. Overview attributes are often abstractions of their detail counterparts: visual (badge for status), semantic (a generated title standing for a conversation), or computational (a calendar of cheapest prices). When the abstraction is computed or generated, the overview stops being a subset of the detail view and becomes a summary in its own right.

Composition

How many of each, and how they nest: several overviews sharing one detail (list + map over the same geographical locations), one overview opening several details, recursion — the pattern nests inside detail views (suggested articles inside an article) — and intermediate detail tiers that soften the jump (tooltip card → full profile). The composition can even invert: a thesaurus entry opens on the detail view, with overviews of synonyms nested inside it — detail-first, the overview arriving second.

Layout

Where the detail opens: side by side, in place, in a popover, or on a new page. Simultaneous split panes — what this pattern is usually reduced to — is just one of these — the one that makes switching a glance rather than a navigation, and the only one that costs width: below roughly 40rem it has nowhere to go, and the detail falls back to opening in place, inside the row it was picked from.

Layout and content are not independent. Opening in place puts the detail directly beneath attributes the overview is still showing, so what reads as orientation when the two views sit apart reads as noise once they touch: the in-place detail is the content dimension minus the overview’s own set, not the same readout relocated.

The control that chooses among them belongs on the detail rather than in a toolbar outside both views — the layout is re-chosen from the thing being laid out, which is also why some detail is always showing.

Resources & references

• Min, Chen, Cao & Xia (2025) Malleable overview-detail interfaces — the content analysis behind the three dimensions, and the malleable form
• Min & Xia (2025) Meridian: a design framework for malleable overview-detail interfaces — the pattern as a declarative specification: data binding, views, malleability
• Cockburn, Karlson & Bederson (2009) A review of overview+detail, zooming, and focus+context interfaces — the spatial-separation branch of the wider taxonomy; combination and preference evidence
• Hornbæk, Bederson & Plaisant (2002) Navigation patterns and usability of zoomable user interfaces with and without an overview — the overview-redundancy finding: a semantic-zoom interface lost time to an added overview, though users still preferred having it
• Shneiderman (1996) The eyes have it — overview first, zoom and filter, then details-on-demand
• NN/g — The anatomy of a list entry — the new-page form’s practitioner treatment; pogo-sticking as the impoverished-overview failure mode
• Tidwell, Brewer & Valencia (2020) Designing Interfaces, 3rd ed. — splits the territory into Two-Panel Selector and One-Window Drilldown by display constraint; prior art for the layout dimension
• van Welie — Overview by detail — the one-pattern precedent in the classic pattern libraries