Skip to content
HalftoneJournal
← All articles

DesignCraft

The details behind density settings

What we kept, what we cut, and why.

Kit Moreau / Dee Marsh

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.

Trade-offs

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.

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.

  • Keep the previous version one click away
  • Report problems in plain language
  • Skip what has not changed
  • Cache what never changes

What changed

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.

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

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

What we would do differently

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.

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.

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

Results

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.

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.

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

What we measured

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

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

  • Report problems in plain language
  • Skip what has not changed
  • Keep the previous version one click away