Animation should answer a question the user is already asking. If it isn't answering one, cut it.
Interface motion has one job: explain a change of state that would otherwise be a jump cut. Where did this come from, where did that go, is the system working. Everything beyond that is a cost paid by every user on every visit.
Our budget
Nothing over 600 milliseconds. Ease-out or a custom curve with no overshoot. One transform property where possible, and never a layout-shifting animation above the fold.
On Orbit School we removed every entrance animation on load and kept motion only for progress and state change. Perceived speed went up and satisfaction followed.
Reduced motion is not a fallback
We design the reduced-motion version as a first-class state, not a stripped one. If the interface only makes sense while it's moving, the interface doesn't make sense.
Related services
The Musebit Agency team
Research, product design and design systems.