Skip to content
NewSee how fast an edit goes live on this site
Halftone

DesignCraft

How we design motion in the editor, part 2

Good defaults, explained.

Jun Calder
Published 2 min read

Motion should explain, not decorate. If an animation does not tell you where something came from or where it went, we remove it. This post covers what we changed, why, and what it means for you.

#Rolling it out

Every color in the product now maps to a role, not a hue. Designers pick "border" or "muted text", and the system decides what that means in light and dark mode.

We tested each change with the people who use the product all day. The best feedback was rarely about how something looked, and almost always about how it felt to repeat.

Hairlines carry more structure than you would expect. A single one-pixel rule can replace a card, a shadow and a background, and the page gets quieter.

“A cache key must include everything that can change the output, and nothing that cannot.”
Lu Brandt

#The constraint

Consistency is a feature you ship once and maintain forever. Our lint rules now catch one-off sizes and colors before they reach review.

Good defaults are invisible. You notice them only when they are missing, usually at the worst possible moment.

We started from the text. Body copy sets the rhythm for everything else, so we fixed its size and line height first and derived the rest of the scale from there.

#What we would do differently

Motion should explain, not decorate. If an animation does not tell you where something came from or where it went, we remove it.

Every color in the product now maps to a role, not a hue. Designers pick "border" or "muted text", and the system decides what that means in light and dark mode.

We tested each change with the people who use the product all day. The best feedback was rarely about how something looked, and almost always about how it felt to repeat.

#The details

Hairlines carry more structure than you would expect. A single one-pixel rule can replace a card, a shadow and a background, and the page gets quieter.

Consistency is a feature you ship once and maintain forever. Our lint rules now catch one-off sizes and colors before they reach review.

Diagram of the request path before and after the change
Figure: the request path, before and after.

#What's next

Good defaults are invisible. You notice them only when they are missing, usually at the worst possible moment.

We started from the text. Body copy sets the rhythm for everything else, so we fixed its size and line height first and derived the rest of the scale from there.

#What we measured

Motion should explain, not decorate. If an animation does not tell you where something came from or where it went, we remove it.

Every color in the product now maps to a role, not a hue. Designers pick "border" or "muted text", and the system decides what that means in light and dark mode.

We tested each change with the people who use the product all day. The best feedback was rarely about how something looked, and almost always about how it felt to repeat.

text
# p95 before / after
build      41.2s -> 6.8s
deploy     18.0s -> 4.4s
end-to-end 11m   -> 1m 52s
How we designour typescaleHALFTONE / JOURNAL

Design4 min

How we design our type scale

What we kept, what we cut, and why.

Cam Okafor
In praise ofour typescaleHALFTONE / JOURNAL

Design10 min

In praise of our type scale

Good defaults, explained.

Eli Tanaka