Interface Lab
Back to knowledge
Interaction Responsive Motion

Feedback States for System Continuity

Loading, saving, generating, review, and failure all need visible states so users know the system is responding.

Design Principle

Missing feedback causes repeated clicks or fear that data was lost.

Principle

Missing feedback causes repeated clicks or fear that data was lost.

Design action

Design pending, success, error, and empty states for async actions; long tasks should show staged progress and last-updated time.

Examples

Positive example: AI generation, uploads, moderation publishing, and admin saves. Counterexample: Buttons do not change after submit.

Apply when

AI generation, uploads, moderation publishing, and admin saves. Requests may exceed 500ms.

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

Design pending, success, error, and empty states for async actions; long tasks should show staged progress and last-updated time.