Sign inSign up

Guidelines for animation timing

In search of the ideal timing for interaction design

Dominic Nguyen
Last updated:

In 1991 there was one website for five billion people. Today, there is one website for every seven people. Massive internet proliferation brought on by 25 years of iteration has given us a growing vocabulary of human computer interactions. Despite the web’s ubiquity, human tendency to copy, and the ease of digital reproduction, I became curious about why user experience inequality still exists and why great design feels right. Given two apps with nearly identical interfaces, what are the differentiating factors that lead to more engaged users?

Interaction design describes what happens in-between states. Unlike other disciplines, it’s focused on the change in state and not the state itself. Since the components of interaction are movement and time, it isn’t inherently suited for static artifacts like sitemaps, mockups, and visual treatments. Adjusting just one of these components has a great affect on what feels right. Today, I’ll explore how time changes user perception.

See for yourself: Airbnb and Yoox’s mobile menus have comparable effects. Yet they feel quite different due to timing.


A delta of tens of milliseconds makes a big difference to the keen observer. Airbnb’s animation feels snappy and Yoox’ sluggish.

Visualizing danger

Humans are the product of hundreds of thousands of years of evolution. Our species existence is a testament to an ability to recognize danger. Sight is among the key factors in determining how safe we feel. Visual properties like contrast, scale, movement and position allow us to make sense of our surroundings. Understanding timing — how long it takes for visual properties to change — helps us identify unnatural elements in our environment.

Imagine walking through the forest and a branch rustles in your periphery. We’ve evolved to register changes (e.g., movement) whose timing doesn’t match our expectations as potentially dangerous. Whether the branch’s motion is the result of a predator or a gust of wind, the momentary unease we end up feeling is the same.

Where does our sense of timing come from? The laws of physics. Because the physical world is our first ‘user interface’ we’ve developed expectations of how things should act through intuition, trial and error. However, when interfacing with computers ideas of what’s ‘physically natural’ are no longer automatic. Immense processing power nullifies the laws of physics for screens and gives digital designers unprecedented control over animation or motion and with it user confidence in the digital environment.

A digital ball is not limited by the same properties of a physical ball

A designer’s intent

Design services efficiency. It is a balance of speed, understandability and confidence. Hasty interactions are difficult to notice and understand. Plodding interactions frustrate the ability to move through a system. Inconsistent interactions cannot instill confidence. To help people accomplish their goals efficiently, we must discover the fastest time where a user retains the ability to understand what’s going on and remain confident in the system.

It’s peculiar that, despite large differences in styling and functionality, popular applications like Gmail, Airbnb, and Dropbox are comparably efficient. Through repeated testing and iteration, their designers determined animation timings that feel good to hundreds of millions of people. We look to the process of human sight to articulate why these experiences feel good.

The journey of an image

The journey from image to thought is a linear path that involves the phenomena of attention and awareness.

  • Attention is a selective process where visual inputs are processed that have a chance of producing or influencing a response. It’s the act of noticing.
  • Awareness is the ability to interpret attention. Whereas attention activates the visual part of the brain, awareness leverages the entire brain to draw connections and provoke understanding.

Attention is unconscious. The brain prevents stimulus overload by conveniently ignoring certain things. Visuals must trigger the signs we’ve evolved to process like contrast, scale, position, and repetition to have the best chance of being noticed. All of this takes place in the first 60–80ms.

Once the visual is noticed it enters the awareness phase. Here pattern recognition and contextualization with needs and goals occurs. However, the event has yet to reach consciousness. You can be ‘aware’ of things and not know it. Awareness occurs at the 100–150ms mark. By the time the event surfaces in consciousness, 150–200ms was spent noticing and understanding.[1]

Limits of human cognition

Though the digital medium defies what is physically possible, we must contend with the limits of human cognition –the biomechanics of how we see and think. There is a minimum amount of time necessary for people to process and understand what they see. Just because designers are able to instantly render interfaces doesn’t mean users will be able to notice or understand what’s been rendered. The more time users have to understand animation the greater chance it has to penetrate consciousness. Where efficiency is concerned, the minimum time to understand stimuli hovers around 150ms.

Waiting game

How long are users willing to wait on animation? Research-backed studies suggest lengthy wait times precipitate abandonment. When an experience feels unnaturally long it gives the subtle impression of being broken. Folks are historically used to software hanging and have thus developed an acute sensitivity for experiences that are ‘not quite right’.

The eye shifts its gaze about three times per second. Humans and most animals assess their environment by tracing a mental map of a scene with their eyes. Since we’re biologically programmed to avoid danger, we don’t have conscious control over the speed or frequency of eye movement. The eye moves as fast as it can and each fixation takes about 350ms[2]. It’s incredible that in one third of a second people notice, understand, and contextualize stimuli then do it all over again and again.

How the eye scans an image

If our goal is to keep users focussed on their current train of thought, then 350ms is a maximum limit before natural instincts encourage the user’s focus to move onto something else. Every extra millisecond not only wastes time but also risks disengagement & distrust.

Managing perception

The quantity of machine effort doesn’t always correspond to how fast people expect products to be. Google combs trillions of data points to deliver the most relevant search results –an incredible feat– yet folks expect pages to appear in less than a second. 99% of sites do far less in more time and no one is up in arms about their performance. How long users will wait is as much about managing the perception of doing work as the actual work itself.

There will be times when data won’t be ready in 150–350ms. Utilizing intermediate states like loading screens & skeleton templates help reassure the user that the app is working on their behalf.

From a users perspective, rapid change is difficult to notice while lengthier change breeds impatience.

The ideal range

Software consists of countless interactions and animations. Those that ‘feel right’ embody an optimal balance of speed, understandability, and confidence. Ideal animation timing is not a single number, but rather a range that accounts for the bio-mechanical & psychological factors of a diverse population. While every use case has its own challenges, let the range of 150ms to 350ms serve as a guideline when timing your product’s animations.

Read more
 [1] Lamme: Why Visual Attention and Awareness are Different (2003)
 [2] Carpenter, R. H. S., Movements of the Eyes, Pion Ltd, 2nd ed. (1988)
 Nielsen: When the UI is too fast
 Nielsen: Powers of 10 Time Scales
 Lindgaard: Attention web designers: You have 50 milliseconds to make a good first impression!
 Google’s 1000/100/6/50ms UI responsiveness guidelines

Originally published at

Did this article help you?

Get free UI development guides and tutorials like this emailed to you.

4,477 developers and counting

We’re hiring!

Join the team behind Storybook and Chromatic. Build tools that are used in production by 100s of thousands of developers. Remote-first.

View jobs

Popular posts

UI Component Playbook

A 5-step guide to designing and engineering frontends with components
Dominic Nguyen
PricingAboutJobsTerms of ServicePrivacyStatusSecurity • SOC 2Contact Sales
© Chroma Software Inc. Made by the maintainers of Storybook.