Lists

A list is a stack of rows that share one shape: a leading icon or avatar, a title, sometimes a line of description, and one thing on the trailing edge: usually broken into groups under their own labels. It is the densest way to present items that are alike enough to compare at a glance but not uniform enough to put in columns.

That trailing edge is where lists go wrong. A chevron means this row takes you somewhere, a switch means this row changes something right here, and a time means the row is only telling you a fact. Mix them inside one group and every row becomes a guess. Keep one kind per group, and if a group has to end in a destructive row, put it last and colour it, so nobody reaches it on the way to something else. Group labels earn their keep too: a few headings turn a scroll into a lookup.

7 blocks

Settings list

Account and workspace settings: grouped rows a person scans once

Settings list, find

Settings long enough that people search: nine rows across three groups

Feature list

Pricing and upgrade pages: what a plan buys, three rows at a time

Inbox list

Notification inboxes: a morning of activity behind three tabs

Inbox list, stacks

Busy inboxes where one source sends many notices

Getting-started checklist

First-run setup: one thing at a time, with how long it takes

Getting-started checklist, rail

Launch checklists where progress should be seen travelling

01

Using Lists

Reach for it when

  • Settings grouped under headings, each row its own destination or switch
  • Inboxes where every row carries read state and a timestamp
  • Short claims read in sequence, like what a plan includes
  • Narrow screens, where a full-width row beats a line of links

Reach for something else when

  • Records compared field by field: a table gives them columns
  • Items with a photo and several unlike stats: a card holds those without cramping them
  • A hierarchy people expand and collapse: a tree view shows the depth
02

Where it shows up

01

Account settings screens

Grouped rows under their own headings, each with an icon chip and either a chevron out to a detail screen or a switch that changes the thing right there, with the dangerous row last.

02

Notification inbox

Rows carrying an avatar or a glyph, a line saying what happened, an unread dot and a time on the right, filtered by a tab track, with one control that marks the lot as read.

03

What a plan includes

An upgrade page written as short rows beside a heading column, each one a claim a reader can check off, ending in a link out to the detail rather than a paragraph of it.

04

Menus on narrow screens

A full-width row is a far bigger target than a link in a paragraph, and the leading icon gives the eye something to aim at when the labels are all much the same length.

03

Questions

What is the difference between a list and a table?

A list is one column of rows that share a shape; a table is a grid of values that share columns. Reach for a table when the reader's job is to compare the same field across many records, sort by it, or scan down one column. Reach for a list when each row is read whole and its fields are not really comparable.

Should a list row be a link or a button?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.