Why timing matters
Users rarely notice good motion. They notice bad motion instantly. Too fast feels broken, too slow feels heavy.
Most transitions we design land between 200 and 400 milliseconds, with a strong ease out so movement starts quickly and settles gently.
The reason is simple. People read motion as cause and effect. When a panel slides in at the right speed, it feels like a direct result of the tap. When it lags, that link breaks and the interface feels like it is thinking instead of responding.
The 100ms threshold
Anything under about 100ms feels instant. That is the window for feedback on a press: a button darkening, a box ticking, a field lighting up. If feedback takes longer, people tap again, and now you have two requests and a confused user.
Our defaults
Hover states take 200ms. Panels and drawers take 400ms. Page transitions take up to 600ms, never more. Anything longer needs a reason.
These numbers are starting points, not laws. Larger elements need a little more time because they travel further. A full-screen sheet might take 500ms where a small tooltip takes 150ms. Size and distance should shape the duration.
Feedback on press: under 100ms
Hover and focus states: 150 to 200ms
Tooltips and small menus: 150 to 250ms
Panels, drawers and modals: 300 to 400ms
Full-screen and page transitions: 400 to 600ms
Easing does most of the work
Duration gets all the attention, but easing is what makes motion feel expensive. A linear move looks mechanical. A move that starts fast and slows at the end feels like it has weight.
We use one ease out curve for almost everything that enters the screen, and a softer ease in out for things that change position. Keeping the set small makes a product feel consistent without anyone noticing why.
Enter: a fast start and a long, soft landing
Exit: shorter than the enter, so the screen clears quickly
Move: ease in out, for elements changing position
No bounce on anything a person needs to read
Write your curves down
We name our curves and put them in the design system, the same way we name colours. Designers pick from the list in Figma, and developers use the same names in code. Nobody types a cubic bezier by hand in the middle of a sprint.
It sounds like housekeeping, but it is the main reason our products feel consistent. A team of eight can ship for a year and every animation still feels like it came from one hand.
Stagger with care
Staggering a list of cards looks great in a demo. In a real product it can make people wait for the content they came for. We cap staggers at around 40ms per item and stop after the first six.
Motion with a job
Every animation should do one of three things: show where something came from, show what changed or show that the system heard you. If it does none of those, it is decoration, and decoration has a cost. It adds load time, distracts from content and gets old by the tenth visit.
We review motion in the same meeting as layout and copy, and each animation has to explain itself. Most survive. The ones that do not were usually there because they were fun to make.
Respect reduced motion
Some people feel dizzy or distracted by movement. When a device asks for reduced motion, we swap slides and scales for simple fades. It takes an hour to set up and belongs on every project.
Reduced motion does not mean no motion. A gentle fade still helps people follow what changed. What we remove is large movement across the screen, parallax and anything that spins or zooms.
Test it on a slow phone
Timing that feels right on a studio monitor can feel sluggish on a three-year-old phone. We always review motion on real devices before handover.
Mid-range Android phones are our benchmark. If a transition holds 60 frames per second on a phone from three years ago, it will be smooth almost everywhere. We animate transform and opacity only, because they are cheap for the browser, and we avoid animating size, shadows and blur on large areas.
We also test with the network throttled. A beautiful page transition is useless if the next page has not loaded. In those cases we show the layout first and let images fade in as they arrive.
A quick checklist
Hover states land in about 200ms
Panels and drawers stay under 400ms
Nothing a person waits on runs longer than 600ms
Every animation has a reduced motion fallback
Motion is reviewed on a real phone before handover
Stick it next to your screen and argue with it when you have a good reason. That is how ours started.


