A preference with history

Dark mode became a mainstream interface preference so quickly that it is easy to forget it was, for decades, a niche choice associated with specific communities: developers, hackers, people who worked at night, people who found bright interfaces physiologically uncomfortable. The preference existed before any platform offered it as a toggle.

When Apple and Google both shipped system-level dark mode in 2019, they were not creating a trend — they were ratifying one that had existed in certain communities for twenty years. The question of what that mainstreaming means for the signal value of dark mode is worth examining.

What the signal said

A dark interface, before it was a system preference, said: I am spending a lot of time here. It said: I came from a tradition — text editors, terminals — that treated the screen as a working surface rather than a presentation layer. It said, sometimes, that I find the brightness of consumer interfaces slightly performative. The dark interface was anti-marketing in a visual sense.

Dark mode began as a refusal of the daylit internet — the web designed to be seen in a coffee shop, in a presentation, in good light. It was a preference for the private screen.

Vera Okafor, MU0ZVV

After mainstreaming

Now that dark mode is a system default for many users, the signal has fragmented. It no longer communicates a specific cultural affiliation; it communicates a personal preference, or nothing at all. This is what happens to aesthetic signals when they are absorbed by platforms: they become options rather than statements.

The response, in communities that valued the original signal, has been predictable. More specific aesthetic choices. Specific colour temperatures, specific terminal colour schemes, specific font sizes. The signal survives, but it moves. It gets more precise.