Skip to content
mh studio Book a free call
← All articles

Motion

Motion with a job: four questions before anything on screen moves

Purpose, duration, easing and a reduced-motion fallback. If an animation cannot answer all four, I cut it.

Mohamed Hassan, Lead Product Designer
· 4 min read

Motion is the easiest part of a product to overdo and the hardest to defend in a review. A designer adds a bounce because it feels nice in the prototype. Six months later the app feels slow, and nobody can say why.

My rule is simple. Before anything moves, I write down four things: what job the motion does, how long it takes, which easing curve it uses, and what happens when the person has asked for reduced motion. If I cannot fill in all four, the animation does not ship. The key tiles in my Motion lab carry those four lines, so you can check me.

1. Purpose: what would break without it?

Motion has a handful of real jobs. It shows cause and effect: I tapped this, that changed. It shows where something came from or went. It explains a wait. And sometimes it adds deliberate friction. Decoration is not on the list.

A useful test: remove the animation and use the screen. If nothing gets harder to understand, the motion was decoration. In Corridor, a concept money app, the card flip earns its place because it shows that the card details are the back of the same card, not a new screen. A plain fade would hide that relationship.

2. Duration: shorter than you think

Most UI transitions should live between about 150 and 300 milliseconds. Feedback on a tap should feel instant, under 200ms. Larger moves, like a panel sliding in, can take 300 or a little more because the eye has further to travel. Anything past half a second needs a reason, and the reason is usually that it is not really a transition. It is a progress indicator or a deliberate hold.

The hold to confirm in Corridor, Stackwise and Relay is the clearest example. It takes about a second, on purpose. That second is the feature: it is how the app makes sure you meant to send money or approve a refund. The fill shows progress the whole time, and releasing early springs back fast, in about 250ms, so cancelling feels as clear as confirming.

3. Easing: match what the motion represents

Linear easing looks mechanical for movement, but it is right for anything that represents time, like a hold fill or an upload bar. When the bar moves at a steady rate, people can predict when it will finish.

For elements entering the screen I use an ease-out curve, fast at the start and gentle at the end, so content arrives quickly and settles. On this site that is cubic-bezier(.215, .61, .355, 1), an ease-out cubic. For things leaving, a quicker ease-in or a simple fade, because nobody needs to watch something go. I avoid bouncy springs in work tools. A bounce on a payroll button reads as a toy.

4. Fallback: what reduced motion actually means

The reduced-motion setting is not a request to remove feedback. It is a request to remove movement that can cause discomfort: large slides, parallax, zooms, constant loops. The information still has to arrive.

So each animation needs a designed fallback. A hold to confirm without the moving fill still has to tell you to keep holding, so the label changes instead. A skeleton loader stops shimmering and stays as a static placeholder. A count-up number simply shows its final value. Parallax and tilt switch off completely, because they carry no information. On this site, the motion layer checks for reduced motion and touch input before it does anything at all.

Where I cut motion

The cuts matter as much as the additions. A few I make often:

  • Staggered list entrances on screens people open twenty times a day. Lovely once, slow by the third visit.
  • Page transitions in dashboards. Ops people switch views fast, and a 400ms slide on every click adds up.
  • Looping decoration next to text people need to read.
  • Any animation that blocks input. If people can tap faster than the animation, the animation should get out of the way.

A spec engineers can build

Handoff is where good motion usually dies. "Make it smooth" is not a spec. For every animation I hand over a line like this one:

Trigger: press and hold Send. Property: fill width. Duration: 1000ms. Easing: linear. Cancel: release before 100% springs back in 250ms ease-out. Reduced motion: no fill, the label changes to "Keep holding".

That one line removes a round of back and forth, and it gives QA something concrete to check. When I review the build, I check the numbers, not only the feel.

The short version

Motion is a product decision, not a finishing touch. Give every animation a job, keep it short, pick easing for what it represents, and design the reduced-motion version on purpose. You will ship less motion, and the motion you ship will make the product feel faster, not slower.

Get new articles first.

Leave your email and get one short note when a new article is out. Nothing else, no spam.

One short email when a new article is out. Unsubscribe with one reply. See the Privacy page for details.