Animation with Restraint: Motion That Communicates
By Maksym Bardakh · Co-founder & President
In short
Motion is most valuable when it communicates: showing where something came from, where it went, and how parts of an interface relate. Used with restraint, animation makes change comprehensible and the interface feel responsive. Used for decoration, it slows the user, distracts, and ages badly. The discipline is to animate to explain, keep it quick, and honor the user’s motion preferences.
Motion is a language, not an ornament
Animation in an interface can do real work. When an element moves from one place to another, the motion tells the user where it went, preserving their sense of where things are. When a panel slides in from an edge, the direction tells the user how to dismiss it. This is motion as communication, and it makes change easier to follow than an abrupt cut would.
The trouble starts when animation becomes decoration, added because it looks lively rather than because it explains anything. Decorative motion has a cost the user pays every time: it takes time, draws attention, and quickly becomes tiresome. The first question for any animation should be what it communicates.
What good motion does
Useful animation tends to serve one of a few purposes, and naming them helps separate motion that earns its place from motion that does not.
- It maintains continuity, showing how a new state relates to the previous one.
- It directs attention to a change the user needs to notice.
- It provides feedback, confirming that an action was registered.
- It expresses spatial relationships, such as where a view comes from and returns to.
Restraint and speed
Even communicative motion must be quick. An animation that the user has seen a hundred times should not make them wait; what felt elegant on first encounter becomes an obstacle by the hundredth. Interface animation should generally be brief, fast enough to clarify without delaying, because the user’s goal is the destination, not the journey.
Honor the user who wants less
Motion is not neutral for everyone. Some users experience discomfort or even nausea from animation, particularly large or parallax-style movement, and operating systems provide a reduced-motion setting precisely for them. An interface that respects this setting, replacing motion with simple transitions when the user has asked for less, treats motion as something offered rather than imposed.
The complete approach is consistent across these points: use motion to communicate, keep it fast, avoid decorative excess, and honor the user’s preference for less. Animation handled this way makes an interface clearer and more responsive without becoming the thing the user has to wait through or wishes they could turn off.
Key takeaways
- Motion is most valuable when it communicates change rather than decorates the interface.
- Good animation maintains continuity, directs attention, gives feedback, and expresses spatial relationships.
- Keep animation brief, since motion the user has seen many times should not make them wait.
- Decorative motion costs time and attention and ages poorly.
- Respect the system reduced-motion setting for users who experience discomfort from animation.
Frequently asked questions
- When is animation worth adding to an interface?
- When it communicates something: maintaining continuity through a change, directing attention, giving feedback, or expressing where a view comes from and returns to. Decorative motion that explains nothing is usually not worth its cost.
- How fast should interface animation be?
- Brief, fast enough to clarify a change without delaying the user, because something seen many times should never make the user wait for a flourish.
- Why respect the reduced-motion setting?
- Because some users experience discomfort or nausea from animation, and the system reduced-motion preference lets them ask for less, so a respectful interface replaces motion with simple transitions for them.
References
About the author
Maksym Bardakh
Co-founder & President
Maksym is a software engineer and product strategist focused on executive-function and behavioral system design. At BBMM he leads product direction across Flowo, TextPack, and Pillow, working at the intersection of human cognition and durable interface design.