Skip to content
SiteMonk Learn
Esc
↑ ↓ navigate ↵ open ⌘J preview
On this page
  1. Give motion a reason
  2. Important information must survive without animation
  3. An inquiry example

Motion and feedback: show customers what happened

Separate decorative animation from useful feedback, including waiting, completion, failure, and reduced-motion experiences.

After customers press “Send inquiry,” they need to know whether the site is processing, has received the request, or needs another attempt. Feedback explains these changes. Motion uses movement, fading, and similar effects to show change.

Feedback can work without animation, and animation does not always provide useful feedback. A design system should decide what needs communicating before choosing how it moves.

Give motion a reason

Purpose Useful approach What to avoid
Processing Clear waiting text with appropriate progress feedback An unexplained spinner that never resolves
A change of state Expansion that keeps related content easy to find Losing the reading position during movement
An outcome Explain receipt, failure, or the next step Only a brief color flash or disappearing message
Brand expression Restrained movement that supports the task Automatic effects covering information or delaying action

Duration is how long a transition takes. Easing describes how its speed changes. The design team sets these details. You can judge whether movement feels slow, interrupts reading, or causes discomfort.

Important information must survive without animation

Some people reduce motion in their device settings; others cannot follow rapid changes. Waiting, error, and completion information must remain understandable when animation is reduced. Automatically starting moving content needs suitable controls; the team can use the W3C design tips when checking this.

Not every section needs an entrance sequence. Key service information and contact options should be available without waiting for a performance to finish.

An inquiry example

After a click, show “Sending.” On failure, explain that receipt is not confirmed and provide appropriate input preservation and retry options. On completion, explain what happens next. Distinguish a booking request from a confirmed appointment. These are design scenarios; they do not establish that real delivery has been tested.

You supply the actual response arrangements and business promises. The team implements the feedback and states. See inquiry and booking forms for receipt checks and loading, empty, error, and success states for the wider pattern.

For our website design service , useful interaction feedback is planned alongside the customer task. If extensive animation is central to your brief, raise it when agreeing scope so we can assess the work.