Design Principle
Turning tables into cards indiscriminately can destroy comparison; choose the pattern by data task.
Principle
Turning tables into cards indiscriminately can destroy comparison; choose the pattern by data task.
Design action
Keep aligned table columns on desktop; on mobile use horizontal scroll or summary cards with expandable details, while key actions remain visible.
Examples
Positive example: Review queues, CRM customer lists, metric rankings, and permission tables. Counterexample: Important columns are hidden on mobile.
Apply when
Review queues, CRM customer lists, metric rankings, and permission tables. Users compare values horizontally.
Source notes
Source note: Synthesized from Apple HIG, Material Design, GOV.UK/Polaris/Atlassian component practices, and interaction accessibility principles. Apple HIG Motion: https://developer.apple.com/design/human-interface-guidelines/motion Material Design Motion: https://m3.material.io/styles/motion/overview/how-it-works GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Shopify Polaris Patterns: https://polaris-react.shopify.com/patterns Atlassian Empty State: https://atlassian.design/components/empty-state
Agent Directive
Keep aligned table columns on desktop; on mobile use horizontal scroll or summary cards with expandable details, while key actions remain visible.