Interaction Design and Usability
Interaction design decides how people and software behave together: what people can do at each moment, how they know they can do it, what happens when they act, and how they recover when something goes wrong. Usability measures the result — whether people can achieve their goals effectively, efficiently, and with satisfaction. Neither is about decoration; a beautiful interface that hides its controls, reacts silently, or punishes mistakes is unusable.
The good news is that decades of research have produced durable principles. They explain why people click the wrong button, why a slow response feels broken, why "Are you sure?" dialogs stop working, and why consistency matters more than novelty. Engineers who know them make better decisions in every component they build — loading states, validation, defaults, and error handling are interaction design.
TL;DR
- Make actions discoverable through affordances and signifiers, and match the user's conceptual model.
- Give immediate feedback and show system status; respect response-time limits (0.1 s, 1 s, 10 s).
- Prevent errors with constraints, good defaults, and confirmation of consequences; prefer undo over "Are you sure?".
- Support recovery: preserve input, explain problems, and make it easy to retry or go back.
- Be consistent with platform and product conventions; favor recognition over recall; use progressive disclosure.
- Evaluate with heuristic reviews and usability tests, not opinions.
Quick Example
Replacing a confirmation dialog with immediate feedback and undo, for a reversible action:
Choosing feedback by expected duration:
Core Concepts
Fundamental Principles
These ideas, popularized by Don Norman, explain most usability problems: a missing signifier, delayed feedback, or a mismatch between the user's model and the system's behavior.
Usability Heuristics
Jakob Nielsen's ten heuristics remain a practical checklist: visibility of system status; match between the system and the real world; user control and freedom; consistency and standards; error prevention; recognition rather than recall; flexibility and efficiency of use; aesthetic and minimalist design; help users recognize, diagnose, and recover from errors; and help and documentation.
Response Times and System Status
People perceive responses within about 0.1 seconds as instantaneous, stay focused up to about 1 second, and lose attention beyond about 10 seconds. Design feedback accordingly: optimistic updates for fast, likely-successful actions; busy states; skeletons; determinate progress for long operations; and background processing with notifications. See Loading, Empty, and Error States.
Error Prevention and Recovery
Frequent "Are you sure?" dialogs train people to click through them; reserve confirmations for consequential actions and name the consequence. See Content Design and UX Writing.
Consistency, Recognition, and Disclosure
Follow platform conventions (where the back button is, how links look) and your own design system, so knowledge transfers. Show options rather than requiring people to remember them (recognition over recall): recent items, autocomplete, visible menus. Use progressive disclosure to keep common tasks simple while making advanced options available.
Interaction States
Every interactive element needs designed states: default, hover, focus, active/pressed, selected, disabled, loading, and error. Focus states are essential for keyboard users; disabled states should explain why when possible; loading states should prevent double submission. Motion can clarify state changes when used purposefully and respectfully; see UI Animation.
Laws Worth Knowing
- Fitts's law: time to reach a target depends on distance and size — make frequent and important targets large and close.
- Hick's law: decision time grows with the number of choices — reduce and group options.
- Jakob's law: people expect your product to work like the others they use.
Evaluating Designs
See Usability Testing and Research Synthesis, UX Research, and Prototyping.
Best Practices
Always Answer "What Just Happened?"
Every action gets visible, timely feedback, and every background process shows its status.
Make Mistakes Cheap
Prefer undo, autosave, and preserved input over warnings and dead ends.
Follow Conventions Unless There Is Evidence
Novel interactions must be clearly better, because they cost learning time.
Test With Real Tasks
Validate designs by watching people complete realistic tasks, not by asking whether they like them.
Common Mistakes
Silent Actions
Confirmation Fatigue
Hidden Controls
FAQ
What is the difference between interaction design and UX design?
Interaction design focuses on the behavior of interfaces — how people act and how the system responds. UX design is broader, including research, information architecture, content, and the overall experience.
What are Nielsen's usability heuristics?
Ten general principles for interface design, such as visibility of system status, consistency and standards, error prevention, and recognition rather than recall, used for quick expert evaluations.
Is undo better than a confirmation dialog?
For reversible actions, usually yes: it keeps people moving and lets them recover from mistakes. Irreversible or high-impact actions still warrant a clear, specific confirmation.
How fast should an interface respond?
Feedback should appear within about 0.1 seconds to feel instantaneous; operations over about one second need visible progress, and those over ten seconds should let people do something else.
How do I evaluate usability cheaply?
Run heuristic reviews and small usability tests with five or so representative users per round, fix the biggest problems, and test again.
Related Topics
- Design and UX — Designing usable products
- Usability Testing and Research Synthesis — Testing with users
- UX Research — Understanding user needs
- UI Animation — Motion that clarifies state
- Prototyping — Trying interactions before building
- Loading, Empty, and Error States — Feedback for async operations