Interaction Design Tutorial: Actions, Feedback and Recoverable Errors
Interaction design specifies how an interface responds to a person's actions over time. This tutorial examines triggers, states, feedback and recovery through tasks such as submitting a form or changing a setting. Describe what the person can do, what the system does next and how the result becomes apparent. Consider waiting, cancellation and failure alongside success so a flow remains understandable beyond its ideal path. Visual styling supports those behaviors, but a static screen alone cannot fully describe them.
Here's a popular Interaction Design video — watch it, then summarize it with one click. Or paste any other YouTube link below.
— or paste your own YouTube link —
Want to keep the key points from a YouTube video? Paste the link below to turn it into structured notes.
Why Use Interaction Design Tutorial: Actions, Feedback and Recoverable Errors
- Describe an interaction as a trigger and a resulting state change
- Make system progress and completion apparent
- Identify missing behavior along error and cancellation paths
- Distinguish reversible actions from consequential commitments
- Document transitions so design and implementation share the same intent
Frequently Asked Questions
What is a state in interaction design?
A state describes the interface's relevant condition at a point in the task, such as editing, submitting or showing a result. Defining states clarifies which actions are available and how the system should respond next.
Why does feedback need to match the action?
People use feedback to understand whether an action registered and what changed. A vague animation cannot replace information about a failed payment or an unsaved edit, because those outcomes require different interpretations and next steps.
When does an action need confirmation?
Confirmation is useful when an action has meaningful consequences and mistakes are difficult to reverse. For frequent, easily reversible actions, clear feedback and an undo mechanism can provide a less disruptive way to manage errors.
How should a form respond after unsuccessful submission?
Preserve useful input, explain the specific problems and make the affected fields easy to find. The person should understand how to continue without reconstructing information or guessing which part of the form prevented completion.
What is the difference between an affordance and a signifier?
An affordance concerns an action that is possible in the relationship between a person and an object. A signifier communicates where or how to act, helping people discover possibilities that would otherwise remain unclear.