Skip to content
Tutorials Center
My learning

Topics

Lesson 21 of 36 ยท Interaction and Visual Design

Interaction Patterns and Feedback

Learn common interaction patterns, the states every control needs, and how feedback, affordances and microinteractions make interfaces feel responsive.

Visual design decides how an interface looks. Interaction design decides how it behaves: what happens when you click, type, drag or wait. A beautiful screen that gives no feedback feels broken; a plain one that answers every action instantly feels trustworthy.

This lesson covers affordances and signifiers, the states every control needs, feedback timing, and a handful of patterns you will use constantly.

Affordances and signifiers

An affordance is what an object lets you do (a button can be pressed). A signifier is the visible clue that tells you so (a raised, colored shape with a label). On screens, affordances are mostly invisible, so signifiers carry the load. Flat text that is secretly clickable fails; an underlined, colored link or a button-shaped control succeeds.

Good signifiers are consistent: if gray rounded rectangles are buttons in one place, do not use them as non-interactive labels elsewhere.

The states of a control

Every interactive element has more than one look. Designers often forget the states that are not the default:

A button is five or more designs

Default Resting, ready to use.
Hover Pointer is over it.
Focus Keyboard focus ring, always visible.
Pressed Active while clicked.

Also disabled, loading, error, and success.

1 / 2
Button states you can feel

The orange outline appears for keyboard users (:focus-visible). Never remove it without a replacement: keyboard and screen reader users depend on it.

Feedback and timing

Users need to know the system heard them. Response time shapes how it feels:

Delay How it feels What to do
Under 0.1 s Instant No indicator needed
About 1 s Noticeable but flows Subtle change is enough
1 to 10 s User loses focus Show a spinner or progress
Over 10 s User leaves Show real progress, allow cancel, or work in the background

Prefer a skeleton screen (gray placeholders that match the layout) or real progress bars over endless spinners, since they set expectations.

Python Choose the right feedback

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Common patterns

  • Forms: one column, labels above fields, inline validation after the user leaves a field, specific error messages next to the field. See also accessible design.
  • Navigation: top bar for websites, bottom tab bar for the three to five main areas of a phone app, hamburger menus only for secondary items.
  • Search: a visible box (not only an icon), suggestions as you type, forgiving of typos, clear "no results" help.
  • Modals and dialogs: use rarely; they interrupt. Always provide a close button, Escape key support and focus trapping.
  • Undo over confirmation: instead of "Are you sure?" for every delete, delete and show "Deleted. Undo". Confirmations are reserved for irreversible, high-cost actions.
  • Empty states: a first-time screen with no data should explain what goes here and offer the next step.
  • Progressive disclosure: show basics first, hide advanced options behind "More options" to reduce overload.

Microinteractions

A microinteraction is one small, contained moment: toggling a switch, liking a post, pulling to refresh. Dan Saffer describes four parts: a trigger, rules, feedback, and loops or modes. A good one confirms the action, is fast (150 to 300 ms), and never blocks the user. Animation should explain (this item moved there) rather than decorate, and should respect the "reduce motion" system setting.

Inline validation with kind messages

The message says what to do, not just what went wrong, and it appears after the user leaves the field instead of while typing.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a signifier?

    Signifiers (labels, shapes, underlines) communicate affordances on screens.
  2. 2. A task takes about 4 seconds and progress cannot be measured. What is an appropriate feedback?

    Between 1 and 10 seconds, show that work is happening; without measurable progress use a spinner or skeleton.
  3. 3. Why is undo often better than a confirmation dialog?

    Confirmation dialogs get clicked through by habit; undo supports flow and still protects users.
  4. 4. Which state must remain visible for keyboard users?

    A visible focus indicator shows keyboard users where they are.

Summary

  • Affordances need visible signifiers; keep them consistent.
  • Design every state: default, hover, focus, pressed, disabled, loading, error, success.
  • Match feedback to response time: instant, subtle, indicator, then real progress.
  • Prefer undo, progressive disclosure and helpful empty states.
  • Microinteractions should be fast, purposeful and respect reduced motion.

Next: Accessible Design: Contrast and Target Size