When dark mode is worth the effort

Every audit we run turns up some version of this. Dark mode is not free, and pretending otherwise leads to bad decisions.

The measurable part of design is whether people can find what they came for and act on it without hesitating. Write the reasoning down alongside the decision, because the reasoning is what changes first.

When it is worth it

Pure black on pure white is harsher than a slightly softened pair. It is worth being explicit about, because assumptions differ quietly. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. That sounds obvious written down. It is still the thing most often skipped.

How to decide

Shadows stop working in dark mode, so borders carry the depth. None of that requires a large budget, only a decision and someone to own it. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

The short version

Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. Three things worth confirming about dark mode before you move on:

• Someone can say what the current setup is without going to look
• Shadows stop working in dark mode, so borders carry the depth — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Most of the value here comes from doing the first two things, not all of them.