Feedback Patterns

owl-listener/designer-skills/interaction-design/skills/feedback-patterns

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Design confirmations, status updates, and notifications that tell users an action registered. Use when the system must acknowledge success or change. For waiting states use `loading-states`; for failures use `error-handling-ux`.

Instructions onlyDesign & Creative
AI-generated overview

Guides design of UI feedback such as confirmations, status updates, and notifications after user actions.

What it does
This skill provides design guidance for system feedback that confirms user actions and communicates status. It covers immediate, confirmation, status, and notification feedback types, plus visual, text, audio, and haptic channels. It also outlines a feedback hierarchy, duration and dismissal rules, and best practices such as matching intensity to action importance and ensuring accessibility.
When to use it
Use it when designing interfaces that must acknowledge a successful action or a change in state. It is intended for confirmation, status, and notification feedback, while waiting states and failure handling are directed to other skills.
Requirements
No tools, packages, runtimes, credentials, or network access are required; it is instructions only and ships no scripts.

Feedback Patterns

You are an expert in designing system feedback that keeps users informed and confident.

What You Do

You design feedback mechanisms that confirm actions, communicate status, and guide next steps.

Feedback Types

Immediate Feedback

  • Button state change on click
  • Inline validation on input
  • Toggle visual response
  • Drag position update

Confirmation Feedback

  • Success toast/snackbar after action
  • Checkmark animation on completion
  • Summary of what was done
  • Undo option for reversible actions

Status Feedback

  • Progress indicators for ongoing processes
  • Status badges (pending, active, complete)
  • Activity indicators (typing, uploading, syncing)
  • System health indicators

Notification Feedback

  • In-app notifications for events
  • Badge counts for unread items
  • Banner alerts for system-wide messages
  • Push notifications for time-sensitive items

Feedback Channels

  • Visual: Color change, icon, animation, badge
  • Text: Toast message, inline text, status label
  • Audio: Click sound, notification chime, alert tone
  • Haptic: Tap feedback, success vibration, warning buzz

Feedback Hierarchy

  1. Inline/contextual — closest to the action (preferred)
  2. Component-level — within the current component
  3. Page-level — banner or toast at page level
  4. System-level — notification outside current view

Duration and Dismissal

  • Toasts: auto-dismiss after 3-5 seconds
  • Errors: persist until resolved or dismissed
  • Confirmations: brief display with undo window
  • Status: persist while relevant

Best Practices

  • Acknowledge every user action
  • Match feedback intensity to action importance
  • Don't interrupt flow for minor confirmations
  • Provide undo rather than 'Are you sure?'
  • Ensure feedback is accessible (not color-only)
  • Test that feedback timing feels right

Source and attribution

Source:owl-listener/designer-skillsininteraction-design/skills/feedback-patternsat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal