Skip to content

Responsive layouts

Rank content and actions by task importance. Source order should make sense when columns stack.

Specify how each structural component changes: sidebar to drawer, table to prioritized rows, settings rail to compact navigation, dialog to sheet.

Opening a mobile detail route should not discard filters, selection, scroll position, or unsaved input without warning.

Maintain touch targets, spacing, focus visibility, keyboard access, and controls that are not hidden under sticky regions or browser chrome.

Use long names, translated labels, large numbers, empty values, errors, many active filters, and several actions—not only ideal mock data.

Review desktop, tablet-like constraints, and mobile in both themes, at increased zoom, and with reduced motion. Breakpoints are implementation tools; usable behavior is the requirement.