Data Tables, Lists & Feeds

Overview

A table is a workspace, not a printout: users scan, sort, select, and act in place. The proven pattern is dense rows + progressive disclosure of actions + persistent user control — sort, filters, and column config survive refresh.

When to Use

• Any screen displaying >10 structured records users must scan, compare, or act on
• Adding sort, filter, column config, bulk select, or inline editing to an existing table
• Choosing pagination vs infinite scroll vs load-more
• Designing empty, loading, and error states for data-heavy views
• Adapting a wide table for mobile
• Reviewing a table users describe as "cluttered," "slow," or "I lost my place"
• NOT for ≤5 items with no comparison need — use a simple list or cards
• NOT for search-results ranking and filter chips (see flow-search)

The Proven Flow