Memorisely
Motion Design

The basics of UI motion

What motion is for in an interface, and the building blocks every designer should understand.

Zander Whitehurst

7 min read

Motion is one of the most misunderstood parts of interface design. Many teams treat it as decoration, something to sprinkle on at the end if there is time left in the sprint. But good motion is not decoration. It explains what just happened, where things came from and where they went. It makes an interface feel responsive, understandable and alive.

The good news is that the basics are not complicated. You do not need to be an animator or a front end specialist to use motion well. You need to understand what motion is for, a handful of building blocks and a few rules of thumb that keep you out of trouble.

What motion is for

Every animation in a product should have a job. If you cannot say what an animation is doing for the user, it probably should not be there. Most useful motion falls into four categories:

  • Feedback. Motion confirms that something happened. A button that presses down slightly when tapped, a toggle that slides across, a checkmark that draws itself after a form submits. Feedback tells people the system heard them.
  • Orientation. Motion shows people where they are. When a panel slides in from the right, users understand it lives to the right and can be dismissed back that way. Spatial cues like this build a mental map of the product.
  • Continuity. Motion connects one state to the next. Instead of a thumbnail disappearing and a full screen image appearing, the thumbnail grows into the full image. The user never loses track of the object they chose.
  • Delight. Occasionally, motion is there to make people smile. A playful success state or a satisfying pull to refresh can give a product personality. Delight is real and valuable, but it should be the rarest of the four.

When you review an animation, ask which of these jobs it is doing. If the answer is none, cut it. If the answer is delight, make sure it is not getting in the way of something people do many times a day.

If an animation is not doing one of these four jobs, it probably should not be there.

The building blocks

Every UI animation, from a hover state to a full page transition, is built from the same small set of ingredients. Once you can see them, you can reason about any animation you come across.

Duration. Duration is how long an animation takes. Most UI motion lives between 100ms and 500ms. Below about 100ms, changes feel instant and the animation barely registers. Above about 500ms, interfaces start to feel slow and people begin waiting for the motion to finish.

Small changes, like a colour shift on hover, sit at the short end. Larger changes, like a modal opening or a drawer sliding across the screen, need a little more time because the eye has further to travel.

Easing. Easing describes how an animation accelerates and decelerates over its duration. Nothing in the physical world starts and stops instantly, so motion with no easing at all, known as linear, tends to feel mechanical.

The most useful default for UI work is an ease out curve, where motion starts fast and slows down as it arrives. It feels responsive because the element reacts immediately, then settles gently into place. A curve like cubic-bezier(0.22, 1, 0.36, 1) is a lovely starting point for elements entering the screen.

Properties. What you animate matters as much as how. Some CSS properties are cheap for the browser to animate, and some are expensive.

transform and opacity are the safest choices. They can be handled by the GPU without recalculating layout, which keeps animations smooth even on modest devices. Use transform: translate() to move things, transform: scale() to grow or shrink them and opacity to fade them.

Properties like width, height, top and margin force the browser to recalculate layout on every frame. They can work for small, isolated elements, but they are the most common cause of janky animation.

Moving, scaling and fading with transform and opacity keeps animation smooth on modest devices.

Choreography. Choreography is how multiple animations relate to each other. When several elements change at once, you decide whether they move together, one after another or in a gentle cascade.

A small stagger, often 20ms to 50ms between items, makes a list feel like it is arriving in an organised way rather than appearing in a block. Too much stagger, and the user ends up waiting for the last item. Choreography is also about hierarchy: the most important element should usually move first, with supporting elements following.

A small stagger makes a list arrive in order without making anyone wait for the last item.

A simple example

Here is a small CSS pattern that combines these building blocks. A card fades and rises into view using only transform and opacity, with an ease out curve and a short duration.

.card {
  opacity: 0;
  transform: translateY(8px);
  transition:
    opacity 200ms cubic-bezier(0.22, 1, 0.36, 1),
    transform 200ms cubic-bezier(0.22, 1, 0.36, 1);
}

.card.is-visible {
  opacity: 1;
  transform: translateY(0);
}

Notice how small the movement is. Eight pixels is enough for the eye to register direction without the card feeling like it is flying in. Subtlety is usually the right call.

Rules of thumb

You will develop your own taste over time, but these rules will keep most interfaces feeling good from day one.

  1. Keep it short. If in doubt, make the animation faster. Around 200ms is a sensible default for most interface changes.
  2. Ease out by default. Elements entering or responding to input should start fast and settle slowly.
  3. Animate transform and opacity. They are smooth, cheap and work almost everywhere.
  4. Move less than you think. Small distances feel refined. Large distances feel theatrical.
  5. Make exits quicker than entrances. When something leaves, the user has already moved on. Do not make them watch it go.
  6. Respect reduced motion. Some people experience discomfort or nausea from movement. Use the prefers-reduced-motion media query to tone down or remove non essential animation.
  7. Be consistent. Similar elements should move in similar ways. Consistency is what makes motion feel like part of the product rather than a collection of effects.

A lesson from the classroom

Early on in my teaching, I ran a session where everyone animated the same simple dropdown menu. One student, a very talented visual designer, produced a gorgeous sequence with a bounce, a blur and a staggered reveal of every item. It looked incredible in isolation. Then we put it into a prototype and asked someone to open the menu ten times in a row. By the third time, they were visibly frustrated. The same student rebuilt it at 150ms with a simple fade and scale, and the room agreed it felt better. That moment taught me more about motion than any principle I had read. Good motion is judged in use, not in a showreel.

The rebuilt dropdown felt better by the tenth open, even though it looked plainer once.

Where to go next

The best way to learn motion is to look closely at products you use every day. Open a menu, close a modal, switch a tab and pay attention to what moves, how long it takes and how it eases. You will start to notice the difference between motion that helps and motion that just performs.

Then start small in your own work. Pick one interaction, give it a clear job, and tune its duration and easing until it feels right. If you want structured practice with feedback from people who do this every day, the AI Motion Design bootcamp covers these foundations and takes you through to building motion in real products.

Motion is not a finishing touch. It is part of how an interface communicates, and once you start treating it that way, your products will feel noticeably better.

Keep reading

View all
View all

Optimize your AI for better experiences, not AI slop.

View all

AI Prototyping Skills

Prototype with AI using clean UI patterns and guardrails so flows feel product-grade, not generic template slop.

$99

AI UI Motion Skills

Motion and micro-interaction patterns that make AI-built UI feel designed, polished, and trustworthy in real products.

$99

Fix AI Slop Skills

Spot AI slop early and fix type, spacing, and components so your product looks intentional, not like a template.

$99

AI Responsive Design Skills

Responsive layout patterns for rails, sidebars, and breakpoints so AI-generated UI adapts cleanly from narrow to wide.

$99

AI Dark Mode Skills

Dark theme tokens, contrast, and surfaces that keep AI-generated UI readable and product-grade, not flat gray on black.

$99

AI Color Token Skills

Neutral and primary ramps with clear steps so AI palettes stay systematic, not a random set of accent hex codes.

$99
View all