On UI Animations

Shu, web developmentdesign
Back

Thanks Paco for bringing up this great topic, and creating the outline of this article while we brainstorming the animation part of our design system. Here're some personal notes that I think worth writing down.

Establish Common Transition Values and Specify Them as Design Tokens

This (using CSS variables for animations) will be very helpful for most of our use cases. I personally prefer ease with a small duration (~200ms) as the transition, but we can define our own easing function too.

Define What Transitions Should Be Used in What Context

We can divide all transitions into 2 groups:

A. Style (opacity, color, background, shadow, border, transform, etc.)

When transitioning a style, the animation should be subtle and it serves the functionality of noticing the user that something has appeared, disappeared, or changed, or simply showing that some element is interactable.

This covers most components such as popover, tooltip, menu, button, link, modal, ... and in this case, we should simply use the CSS variables defined based on the varying property.

B. Layout (top, left, bottom, right, height, width, etc.)

When transitioning the layout, we usually want to show the logic of the UI implicitly to the user, so they will have the sense of.

Things with a fixed layout (so the animation will have a fixed timing and range). They should be tweaked case by case, e.g.: feedback input and toast.

For things which we can't predict the size and position (they change based on the dynamic content), e.g.: file tree, collapse, show more, drawer..., there're 2 difficulties:

In this case, we should use spring animations (e.g.: react-spring, react-motion) with ResizeObserver to measure the size dynamically, which is a better practice in the sense of both design and engineering.

When Is No Animation Desirable?

CC BY-NC 4.0 © Shu Ding.RSS