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

Design

How we design our type scale, part 2

The small decisions that make the product feel quieter.

How we designour typescale, part 2HALFTONE / JOURNAL
Bo Lindqvist
Published 2 min read

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. This post covers what we changed, why, and what it means for you.

#What we measured

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.

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

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.

  • Cache what never changes
  • Run independent steps in parallel
  • Keep the previous version one click away
  • Skip what has not changed

#Where we started

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.

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

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

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

#Trade-offs

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 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.

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

#What we would do differently

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

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.

  • Keep the previous version one click away
  • Run independent steps in parallel
  • Cache what never changes

#Results

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.

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

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.
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