Skip to content
Back to blogs

UI animation

TL;DR: UI animation should communicate a change or response. Keep essential information available without movement, respect reduced-motion preferences and let people pause ongoing animation when needed.
Long-exposure light trails sweeping past the New York skyline at dusk

Photography by Davide Cantelli / Unsplash

In this article

Introduction

UI animation is movement in an interface that communicates a transition, response or change of state. It can help people follow what happened after an action. Use it where that explanation is helpful, and keep the task understandable when motion is reduced or disabled.

Give movement a job

A panel opening from its control can explain where it came from. A selection state can confirm an action. A transition can preserve someone’s place between views. Each movement should answer a question about the interaction.

Decorative motion needs separate judgement. It should not hide instructions, delay repeated actions or become the only way to understand a result.

Explain what changed

Decide what the visitor needs to notice: a new state, an available control or the outcome of an action. Then consider whether movement communicates it more clearly than a static change.

  • Orientation: does the transition explain where a new view came from?
  • Feedback: does movement help someone recognise that an action had an effect?
  • Attention: does it point towards information that needs to be noticed?
  • Continuity: does it preserve a sense of place while the interface changes?
  • Control: can people use the product when continuous movement is paused or reduced?

Plan useful motion

Describe the purpose before choosing the effect. Plan the reduced-motion version alongside the animation, with the same information and controls available.

Connect the beginning and end states

A transition needs a clear relationship between its two states. When a project card opens, movement can connect the chosen card with the detail view. When a menu expands, the change should leave someone able to identify the navigation and the way back.

Describe the final state before tuning the motion. Check its hierarchy, text and controls while still. Then add the transition and ask whether someone finishes it with a clearer understanding of what happened. Movement should support a legible interface rather than compensate for an unclear end state.

Match the pace to repeated use

A first introduction and an everyday action have different rhythms. Someone may watch an opening sequence once, but use a filter or change a selection many times. Review the animation over several repetitions to see whether its pace still suits the task.

Keep important actions available and consider interruptions. A person may choose another item before the current transition ends or decide to close a panel immediately. The interface should reach a clear state and accept the next useful action without depending on a perfectly timed sequence of inputs.

Design the reduced-motion experience

Identify which information must remain visible when movement is limited. A selection still needs a clear state, an update still needs useful feedback and a newly opened view still needs a readable structure. Reduced motion is an experience to design, not an empty version of the page.

W3C’s Pause, Stop, Hide guidance describes controls for certain automatically moving or updating information. Review the relevant criteria when planning continuous effects. A visible pause control and respect for motion preferences are practical parts of a wider accessibility review; they should be checked alongside reading order, focus and keyboard use.

Plan the interaction with and without movement
SituationPurposeful movementStill or reduced-motion treatment
Opening a detail panelConnect the selected item with the new viewShow the view with a clear heading and close control
Changing a material previewMake the changed selection understandableKeep a visible selected state and updated preview
Continuous decorative sceneAdd atmosphere without competing with contentProvide a readable static composition and motion control

Test motion in use

Try repeated actions, keyboard navigation and reduced-motion settings. Check that content stays readable and that ongoing movement can be paused where appropriate.

  1. Write the purpose. Describe what each movement helps a visitor understand. If the purpose is purely expressive, check that it leaves the task and text easy to use.
  2. Check the still states. Review the interface before and after the animation. Confirm that the content, controls and selected state remain understandable without the transition.
  3. Repeat the task. Open the menu, change the filter or explore the cards several times. Look for waiting, unnecessary movement or feedback that becomes distracting.
  4. Try interruptions. Change direction, close a panel or make another selection while the interface is responding. Confirm that the result stays clear and the controls remain usable.
  5. Review motion preferences and controls. Use the reduced-motion setting and the page’s pause control where available. Check that the primary content and task are still available.

Avoid unnecessary movement

Watch for delayed buttons, unexpected page movement and repeated decoration around reading tasks. Remove effects that compete with the decision the person is trying to make.

  • Animating every element so that the visitor has to wait for the page’s basic message.
  • Using continuous movement beside text without considering reading and user control.
  • Making an important state or explanation depend entirely on the animation.
  • Ignoring repeated use, interruptions or a person’s preference for reduced motion.
  • Reviewing only a large display instead of checking the interaction on a phone and with a keyboard.

Frequently asked questions

What is the purpose of UI animation?

UI animation can explain a change, provide feedback or show a relationship between states. It can also add visual character when that suits the experience. Define the job of a movement before deciding its appearance or duration.

How much animation should a business website use?

Use the amount that supports the content, brand and visitor’s task. Review whether people can read, navigate and act while movement is happening. There is no useful universal count of animations for every page.

What is a reduced-motion experience?

It is a version of the interaction that limits movement while preserving the content, state and controls people need. A transition may be simplified or removed, with a clear final state retained. The treatment should be planned for the actual interface.

Does a pause button make an animated website accessible?

A pause control addresses only part of the experience. Focus, keyboard interaction, reading order, contrast and other considerations still need review. Check the relevant accessibility requirements and test the complete task rather than treating a single control as a guarantee.

How should an animation brief describe the work?

Include the purpose, trigger, starting state, final state and behaviour during interruption. Describe the reduced-motion treatment and any pause controls as well. This gives the team a shared way to review both the effect and its use in the product.

Conclusion

Give each movement a specific purpose and keep the interaction useful without it. Review motion alongside accessibility, content and repeated use. Our content and motion services connect the message with the experience.

Sources and further reading

All articles

Let’s make a start

Tell us what
you have in mind.

Choose a service to start the conversation.

Continue with AI development & generative AI