Skip to content
UXE Award

Interaction design that earns its motion

Interaction and feedback is one of the seven UXE criteria — and the one most often mistaken for animation. What editors score: response times, state changes, undo over confirmation, and motion that does a job.

The UXE editors5 min read

Interaction and feedback is the criterion teams assume is about animation. It isn't. It's about whether the product answers — clearly, promptly, and in a way that says what happened. Most of the score is decided in the first 100 milliseconds after a click, long before anything has a chance to animate.

The three timings that decide the feel

Response budgets
  • < 100ms

    Feels instant

    The window for acknowledging an action: a pressed state, a focus change, a value updating.

  • < 1s

    Feels continuous

    Thought is unbroken. No indicator needed, but the interface must not appear frozen.

  • < 10s

    Attention held, barely

    Needs a progress indicator with a real sense of how far along it is.

  • > 10s

    Gone

    Let them leave. Do the work in the background and tell them when it's done.

These are long-established human-factors thresholds, and they still describe how products feel.

The distinction that matters: responding is not finishing. A button that shows it was pressed within 100ms buys several seconds of patience for the work behind it. A button that does nothing until the work is done feels broken at 400 milliseconds.

Every state, designed

A control has more states than most design files contain: default, hover, focus, active, loading, success, error, disabled — and, for a toggle, each of those in both positions. Editors find the gaps by tabbing through and by breaking things on purpose.

Five states editors look for
Compared onPresentMissing
FocusVisible, distinct from hoverRemoved with the default outline
LoadingIn place, same size, no layout jumpWhole section replaced by a spinner
SuccessBrief, in context, then out of the wayA toast in the corner nobody sees
ErrorAt the control, keeps the inputAlert dialog that loses the work
DisabledExplains what's missingGreyed out, no reason

Undo beats confirmation

"Are you sure?" is a design that moves the cost to every user to protect against a rare mistake. After the third dialog, nobody reads them — so the protection stops working while the cost continues.

For anything reversible, act immediately and offer undo. Reserve confirmation for the genuinely irreversible, and when you do confirm, restate the specifics: Delete 3 invoices beats Yes. Products that get this right feel faster without being faster.

Motion with a job

Motion in a scoring product does one of three things: it shows where something came from, it maintains continuity across a change of context, or it confirms an action landed. Anything else is decoration — charming once, then a tax paid on every repetition.

Two kinds of motion

Earns its place

  • A sheet rising from the control that opened it
  • A row settling into its new sorted position
  • A 120ms press state
  • A skeleton that becomes the content, in place

Costs you

  • A 600ms page transition on a daily task
  • Staggered entrance animations on a list of 200
  • Parallax that ignores reduced-motion
  • A loading animation longer than the load

And all of it must respect the reduced-motion setting. Ignoring that preference isn't a style choice — for people with vestibular disorders it's a product that makes them unwell, and it costs points under two criteria at once.

Feedback that says what happened

  • In context, not in a corner. Confirmation belongs where the action happened; a toast 800 pixels away is easy to miss.
  • Specific. "Invoice 4417 sent to maya@example.com" beats "Success!".
  • Persistent when it matters. Anything the user might need to act on shouldn't disappear on a timer.
  • Announced. A visual-only confirmation doesn't exist for a screen-reader user.

What to send

A short screen recording is worth more than any still here — twenty seconds of the key flow, at real speed, including a failure and a recovery. Add your state inventory if you have one, and note where you chose undo over confirmation.

Interaction is the focus criterion for Interaction Design and weighs heavily in Mobile Experience — but it's scored on everything. Enter a project.

Gestures, and the cost of inventing one

A custom gesture is a feature only the people who read your release notes will ever find. Every invented interaction has to be taught, remembered and forgiven — and it must always have a visible alternative.

  • Never make a gesture the only route to an action.
  • Follow the platform's conventions before your own: swipe-back, pull-to-refresh, long-press for context.
  • Make destructive gestures confirm, and make them hard to trigger accidentally.
  • Anything draggable must also be achievable without dragging — a WCAG 2.2 requirement and, practically, how trackpad and switch users work.

Optimistic interfaces and honest reconciliation

Showing the result before the server confirms it is one of the strongest tools available for perceived speed — and one of the easiest to do dishonestly. The rule is that the optimistic state must be recoverable: if the write fails, say so where the change appeared, restore the previous state, and keep whatever the person typed.

Optimistic updates, done honestly
  1. 01

    Act immediately

    Reflect the change in the interface without waiting.

  2. 02

    Mark it in flight

    Subtly — a dimmed state, a pending mark. Not a spinner over everything.

  3. 03

    Confirm quietly

    Remove the pending mark. No celebratory toast for a routine save.

  4. 04

    Fail loudly

    At the point of change, with the content preserved and a retry.

Sound, haptics and the senses nobody budgets for

Haptic feedback is the most under-used channel on mobile and the easiest to overdo. One rule holds: haptics confirm, they do not decorate. A short tap on a successful action, a distinct pattern for an error, nothing on scroll. And every one of them must be silent when the system asks for it.

Questions we get asked

  • Is animation required to score well on interaction?

    No. A product with almost no animation and excellent state handling scores higher than a heavily animated one with missing feedback. The criterion is about response, not motion.

  • How fast should a transition be?

    Most interface transitions land between 150 and 300 milliseconds. Below that they read as instant; much above and they start costing time on repeated tasks.

  • What's the most common interaction failure in entries?

    A missing or invisible focus state, followed closely by a success message that appears somewhere the user isn't looking.

  • Should everything have an undo?

    Everything reversible should. Reserve confirmation dialogs for the genuinely irreversible, and when you use one, restate exactly what will happen on the button itself.

Assessed work that scores highest on interaction & feedback

Chosen by score from the work the editors have assessed, not by hand.

  • interaction
  • motion
  • feedback
  • scoring

Written by

The UXE editors

The team that selects the work, uses it, scores the seven criteria and writes every verdict on this site.