interaction design
Feedback
What is feedback in UX?
Feedback is the interface answering back: a clear sign of what just happened and what to do next. Act without it and people are left guessing whether anything worked at all.
Also known as: system feedback, interface feedback
Prefer to watch?
Watch the recap 0:31
The demo
Click the button below to send the transfer. Observe what happens (or doesn't happen) when feedback is absent.
Warning: duplicate submissions
You clicked the button 0 times because the screen was silent. In a live system, this could initiate multiple duplicate transfers totalling £0 to Jane Doe.
Click the button below to send the transfer. Observe how hover states, disable logic, and success messages keep you informed.
What this demo shows (text version)
An interactive comparison showing the impact of user interface feedback. The user is presented with a standard funds transfer form with two demo variants.
In the 'Silent UI' view, clicking the submit button provides no visual transition, state change, hover state, or loading spinner. During a simulated 2.5-second lag, users tend to click repeatedly, which increments a counter highlighting the cost of duplicate submissions. The page then silently resets to blank.
In the 'Responsive UI' view, elements feature focus and hover highlighting. Clicking the button immediately disables it to prevent duplicate clicks, shows a loading spinner, displays a countdown progress bar, and presents a clear transaction success dialog when complete.
Feedback is the interface answering back - a clear sign of what just happened and what to do next. Acknowledge every action with a state change (a spinner, a disabled button, a confirmation), or people click again, unsure anything worked, and quietly lose trust in the thing.
The silent form left you clicking into the void, unsure anything had happened - so you clicked again. That uncertainty is the cost of missing feedback: every unanswered action invites a repeat.
Feedback has to be quick. A few hundred milliseconds of nothing reads as "broken", and a broken-feeling button gets pressed again - which is how you end up with duplicate payments.
The cheapest feedback is often the most valuable: disable the button the instant it is pressed, then say plainly when the thing is done. Confirmation isn't decoration, it is how people know they can stop.