Interaction Design Basics
Level 4 · Designing the interaction
How a product answers when you tap, type or swipe. Affordances, signifiers, feedback and the tiny moments built round one task.
Course contentsLesson 14 of 21
Level 1 · What UX is
Level 2 · Finding out from users
Level 3 · Making sense of research
Level 4 · Designing the interaction
After this lesson you can
- Tell an affordance from a signifier
- Give every action clear feedback
- Break a microinteraction into parts
11 mincovers 5 glossary entries
Worth reading first: Wireframes and Prototypes
How a product answers what you do
Interaction design is how a product answers when you tap, type or swipe. Each action should get a clear reply, fast. A reply within a tenth of a second feels instant. After about one second, people notice the wait. After ten, many give up or start doing something else.
An affordance is what an object lets you do. A handle can be pulled. A button can be pressed. A text box can be typed in. The word comes from a psychologist, and a design writer brought it into everyday design in 1988.
A signifier is the clue that shows what you can do. A push sign on a door is a signifier. So is the shadow that makes a button look raised, or the blinking line in a text box. An affordance nobody can see is useless, so most design work is really about signifiers.
The classic failure is a door with a pull handle that has to be pushed. The handle signals pull, the door wants push, and everybody gets it wrong. On a screen, the same thing happens with flat text that is secretly a link, or a gray button that does work.
Feedback is how a product shows what just happened. A button darkens when pressed. A tick appears when a message is sent. A spinner shows that work is going on. Without feedback, people press again, and the order goes through twice.
A microinteraction is a tiny moment built round one task. The heart that pops when you like a post is one. So is a switch that slides when you switch on dark mode. Each has a trigger, rules for what happens, feedback, and what changes if it repeats.
The common slip is to treat feedback as decoration. An animation that looks nice but says nothing is noise. Good feedback answers a question the user has right now. Did it work? Is it still going? What changed?
Worked example
A payment button that was pressed twice
A ticket site's pay button did nothing visible for 4 seconds while it worked. About 1 in 50 buyers pressed it again and paid twice.
The team made the button change into a spinner with the word paying the moment it was pressed. Double payments almost stopped.
The words for this lesson5
Check yourself
A door has a pull handle but must be pushed. What has gone wrong?
Finished this lesson?
Marking it complete also marks its 5 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.