All notes
Experience3 min readNote / 03

Motion should have a purpose.

A transition can do more than look good. It can show direction, connect two states and help someone understand what just happened.

The space between states matters

Interfaces are often designed as still screens. Before and after sit beside each other, while the moment connecting them waits until later. But someone opening a panel, deleting an item or moving to a new screen experiences that interval too. Motion can explain how two states relate and become part of the product's language.

A card expanding into its details can suggest where the new information came from. A panel arriving from the edge can explain its relationship to the main content. These small spatial cues help someone follow the change. Instead of feeling as though the interface has started over, the experience keeps a sense of continuity.

Give each movement a job

The first question when designing motion is what it should communicate. Does it reveal a change of state? Move attention to new information? Show that a task is still in progress? A clear job gives the decisions about timing and shape a useful foundation.

A brief change to a save button can confirm that an action succeeded. An extended bounce adds attention without adding information. An item appearing gently in a list can help someone find the result of their action. Animating every item in sequence might introduce a wait for the same information. Each movement needs to earn the attention it asks for.

Before motion asks for attention, it should have something to say.

Rhythm matters as much as speed

Making every transition faster does not automatically make a product feel more fluid. A very short movement may go unnoticed; a long one may interrupt the task. Useful timing depends on the size of the change and what someone is trying to accomplish. A button's response and an entire screen change can benefit from different rhythms.

Repetition also changes how a delay feels. An elaborate introduction might look pleasant once and become tiring on every return. It helps to consider an animation as part of ordinary repeated use, alongside its isolated preview. Fluidity can come from a shorter duration, a smaller movement or simply an immediate response.

Offer another way to follow the change

Motion can be uncomfortable for some people. Large movements, zoom effects and continuous repetition deserve particular care. Someone who chooses reduced motion in their system should find that preference respected inside the product too. The essential meaning should remain available in a comfortable form.

Text, colour and a clear change in layout can support feedback without relying on animation. A spatial transition can be shortened or replaced with a direct update. The goal is to communicate the same change in a suitable way. Keyboard focus and the outcome of an interaction should also remain available without waiting for an animation to finish.

Ask what it makes clearer

A useful final check is to imagine removing the transition. Would someone lose a relationship or a piece of feedback? If not, the movement may be a small expression of the product's character. There is room for that too, provided it leaves the main task responsive, keeps information available and avoids competing with everything else on the screen.

For Litken, good motion strengthens what an interface is saying. It responds to an input, makes a change visible or helps explain the next step. It can be quiet and still do valuable work. The product stays calm, while its parts feel connected.