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

DesignCraft

How we design dark mode

The small decisions that make the product feel quieter.

How we designdark modeHALFTONE / JOURNAL
Jun Calder / Dee Marsh
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 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.

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.

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

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}/` };
}

#Where we started

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.

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.

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

#What's next

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.

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.

“Good defaults are invisible until they are missing.”
Dee Marsh

#Rolling it out

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

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.

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

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.

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