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

DesignCraft

How we design empty states, part 2

The small decisions that make the product feel quieter.

How we designempty states,part 2HALFTONE / JOURNAL
Gus Heller / Lu Brandt
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.

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

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.

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

#Where we started

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.

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.

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

ts
const key = `${route}:${hash(content)}:${hash(template)}`;
const hit = await cache.match(key);
if (hit) return hit;

#What changed

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.

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

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

#What we would do differently

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.

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.

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.

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

#What's next

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

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

“A cache key must include everything that can change the output, and nothing that cannot.”
Ivo Santos
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