Skip to content
NewSee how this site publishes in seconds
Halftone

DesignCraft

How we design dark mode

Good defaults, explained. What we kept, what we cut, and why. The small decisions that make the product feel quieter.

How we designdark modeHALFTONE / JOURNAL
Gus Heller
Published 2 min read

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

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

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

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

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

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.

#The constraint

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.

ts
export async function publish(post: Post) {
  const problems = validate(post);
  if (problems.length) return { ok: false, problems };
  await commit(post);
  return { ok: true, url: `/blog/${post.slug}/` };
}

#What we measured

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.

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

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

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

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.

#Rolling it out

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.

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

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

How we chose, tested and shipped the details. Good defaults, explained. What we kept, what we cut, and why. The small decisions that make the product feel quieter.

Jun Calder / Gus Heller
The detailsbehinddensitysettingsHALFTONE / JOURNAL

Design4 min

The details behind density settings

The small decisions that make the product feel quieter. What we kept, what we cut, and why. Good defaults, explained.

Gus Heller
In praise ofour typescaleHALFTONE / JOURNAL

Design10 min

In praise of our type scale

How we chose, tested and shipped the details. The small decisions that make the product feel quieter. Good defaults, explained.

Dee Marsh / Jun Calder