frameworkExperience & interface

Split View and Window Splitter

A split view shows related panes together, while a window splitter is the operable divider that lets users change their relative size.

Download Markdown (.md)

01What it means

A split view divides one window into adjacent panes, often using a list-detail or source-preview relationship. A window splitter is a movable or fixed separator that resizes or collapses a pane. A split view can exist without user resizing, but an operable splitter requires focus, value, orientation, and keyboard behavior.[1][2]

02Why it matters

Simultaneous panes reduce navigation and preserve selection context during comparison or editing. Responsive collapse and accessible resizing are necessary so the layout does not become cramped or trap controls outside the usable viewport.

03When to use it

Use a split view when two related contexts need frequent coordinated use, such as a message list and message detail. Use sequential pages on narrow screens or for simple journeys, and add a splitter only when users benefit from controlling pane size.

04How it works

  1. Define each pane’s purpose, minimum useful size, priority, and relationship to the current selection.
  2. Choose fixed, collapsible, or user-resizable proportions and a responsive threshold for sequential presentation.
  3. Give an operable splitter a visible handle, label, orientation, current value, and keyboard controls.
  4. Preserve selection, focus, scroll, and user sizing when panes open, close, or the window changes.
  5. Test small windows, zoom, long content, right-to-left layouts, screen readers, and restoration after collapse.

05A practical example

Example

An email client shows folders, a message list, and the selected message in adjacent desktop panes. Users can resize the list-detail separator with pointer or arrow keys; on a phone, selecting a message opens a separate view and Back returns to the same list position.

06Where it breaks

Multiple panes reduce space for each task, add focus and scrolling complexity, and translate poorly to compact screens. User-resizable layouts require stored preferences and sensible recovery when saved sizes no longer fit.

Common mistakes

  • Shrinking panes below a usable size instead of changing the responsive presentation.
  • Making the splitter operable only by precise pointer dragging.
  • Losing list selection or scroll position when the detail pane closes.
  • Treating a decorative divider as an adjustable splitter without communicating its behavior.

07Sources

  1. Window Splitter PatternW3C Web Accessibility Initiative · Technical guidanceWindow Splitter Pattern
  2. Split viewsApple · Institutional guidelineSplit views
View saved topics

Start typing to search titles, definitions, categories, and frameworks.