Dreabuild
000 %
Loading
← All notes
Craft 6 min

Motion that earns its place

Every animation on a site is a small tax on the person using it. Here is the test we run before any of ours ships — and the three questions that kill most of them.

Written by , COO & UI/UX Designer

Notes from the studio: motion that earns its place

The tax nobody accounts for

An animation is never free. It costs the visitor time they did not ask to spend, it costs the browser frames it could have spent on something else, and it costs the next engineer a paragraph of explanation. Most of the motion on most sites is not paying that back.

We are a studio that leads with motion, so we get accused of the opposite problem. Fair. The difference is that we make every effect argue for itself first.

The three questions

Before anything scroll-driven or hover-triggered goes into a build, it has to survive three questions.

Does it explain something? Good motion answers a question the visitor was already asking: where did that panel come from, what just changed, how much further is there to go. A progress rail that fills as you read a process is doing work. A logo that spins on load is not.

Does it survive being seen twice? The second viewing is the honest one. Anything that delights on first load and irritates on the fourth is a liability, because the people who matter most — the ones who come back — get the fourth version.

Does it degrade to nothing? Turn it off entirely. If the page still makes sense, the motion is a layer. If the page breaks, the motion was load-bearing and it should not have been. Every reveal we write has a resting state that is the finished, readable state.

What we cut last month

A parallax on a testimonial block, because it explained nothing. A staggered letter reveal on a page header, because it delayed the one sentence the visitor came for. A hover tilt on a card grid, because it fought the cursor.

None of that was bad work. It just could not answer the questions.

What we kept

The things that survived tend to share a shape: they are tied to scroll rather than to a timer, so the visitor sets the pace; they move a real object rather than decorating a static one; and they finish. Motion with an end state feels designed. Motion that loops forever feels like a screensaver.

That is the whole method. It is not sophisticated. It is just applied consistently, which turns out to be the hard part.

Next note The seam between design and engineering

Got a project that needs this kind of attention?

Start a project