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.
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.
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.
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.
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.
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.
If the row goes somewhere, make it a link, so it can be opened in a new tab, copied, and read as a destination. If it acts on the spot, make it a button. If the row carries a switch, the row itself should not be clickable at all, or the switch and the row will fight over the same press.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
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.
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.
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.
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.
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.
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.
If the row goes somewhere, make it a link, so it can be opened in a new tab, copied, and read as a destination. If it acts on the spot, make it a button. If the row carries a switch, the row itself should not be clickable at all, or the switch and the row will fight over the same press.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Manage your profile, team and preferences
Manage your profile, team and preferences
Manage your profile, team and preferences
Manage your profile, team and preferences