Motion with a purpose

We use motion to show where things come from and go, to connect a click to its result, and to guide the eye, always in service of understanding, never just for show.

A well-timed transition tells the eye where something came from and where it went, so the interface feels coherent instead of jumping. Motion for its own sake does the opposite, it draws attention to itself and slows everyone down.

We use animation to show cause and effect, preserve context across changes, and reassure users that the system heard them, and we keep it fast enough that it never becomes the thing you're waiting on.

Every animation should answer a question the user didn't know they had: where did that panel come from, what just saved, why did this item leave the list? Motion that explains causality earns its milliseconds; motion that only performs charisma steals them.

Duration is a language. Micro-feedback lives under 150ms, spatial transitions around 250, 350ms, and anything past half a second had better be entertaining a genuine wait. When an interface feels sluggish, the animations are usually correct but too long.

We build on transforms and opacity for buttery frame rates, respect prefers-reduced-motion as a hard requirement, and prototype timing on the slowest device we own, animation that only looks good on a designer's laptop is a private joke.