Quick Reference For Interaction Feedback
Recall the feedback states every consequential action should cover.
What are the minimum states for a consequential submit action? Idle, active/pressed, processing, success, recoverable error, and retry. These states cover the user loop from intent through outcome. Spinner only vs status message Motion needs meaning when risk is high. Engineering can infer the states later. Your line If the state affects user trust, copy, retries, or QA, it belongs in the design spec now. Let implementation invent interaction behavior. State behavior is product behavior, not styling. What should success feedback prove? What changed, where it changed, and what the user can do next. A generic toast often confirms too…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in