Dark mode has grown from a trendy option into a standard feature users expect. Operating systems offer it device-wide, and browsers pass that preference on to applications. Still, a dark theme is not simply inverting colors or swapping a white background for black. A poorly executed dark mode can reduce readability, undermine your brand identity and create more problems than it solves. In this article we explain when dark mode really makes sense, how to implement it properly from a technical standpoint and which mistakes we see most often in practice.
What is dark mode and why do users want it?
Dark mode is a variant of the user interface in which light text and elements sit on a dark background. Unlike the classic light display, the focus is on reducing the total amount of emitted light. Users choose it for several practical reasons:
- Comfort in low-light environments. A dark display is easier on the eyes when the surroundings are dark, for example in the evening or in a dimmed room.
- Energy savings on certain screens. On OLED and AMOLED panels, black pixels are practically switched off, which can extend battery life.
- Aesthetic preference. To many users a dark interface simply feels more focused and modern.
- Less fatigue during long sessions. Developers, designers and people who look at a screen for hours often report less eye strain.
It is important to understand that dark mode is not universally better. It is an option that depends on context, content and your audience’s expectations.
When does dark mode make sense, and when does it not?
Before you invest time in implementation, ask a simple question: does a dark theme really serve your users, or are you introducing it just because it is trendy? There are situations where it delivers clear value and others where it is an unnecessary complication.
Situations where we recommend dark mode
- Applications and tools people use for long stretches, such as dashboards, admin panels and development environments.
- Content consumed in the evening, for example reading, streaming or messaging apps.
- Products with a technical audience that explicitly expects a choice of theme.
- Text-heavy interfaces where users spend hours in the same view.
Situations where dark mode is not a priority
- Brochure sites and marketing websites with a strong visual identity tied to a light palette.
- Content rich in product photos, where a dark background changes how colors are perceived, which is especially sensitive in online stores.
- Projects with a limited budget where other features matter far more to users.
If you are not sure, start with data. Look at how many of your visitors use dark mode at the system level and what your audience profile looks like.
Technical implementation: from CSS variables to system preferences
A solid dark mode rests on a color architecture, not on retrofitting. The cleanest approach is to use CSS variables that define semantic colors and then switch them depending on the theme.
If you are thinking about a new or better website for your company, see how we approach website development for clients in Sarajevo and across Bosnia and Herzegovina.
1. Define semantic color tokens
Instead of repeating specific color values throughout the code, define variables by meaning. For example background, primary text, secondary text, borders and accent. That way you change the theme in one place, not in a hundred locations.
2. Respect the system preference
Browsers report whether the user prefers a dark display through the prefers-color-scheme media query. Your default theme should follow that signal so users immediately get the display they expect.
3. Allow manual selection
The system preference is a good starting point, but users should be able to switch the theme manually. Three options are standard: light, dark and automatic based on the system. Save the choice locally so it is remembered on the next visit.
4. Avoid a flash of the wrong theme
A common mistake is the so-called flash, when the page briefly appears in the light theme before the dark one loads. That is why the theme must be applied as early as possible during loading, before content is rendered, so the user does not see an abrupt switch.
The design rules broken most often
The technical side is only half the job. A quality dark mode requires careful design decisions. Here are the mistakes we see most often and how to avoid them.
- Pure black background. A completely black background with completely white text creates too much contrast and is tiring. Use a very dark gray instead of pure black.
- Pure white text. Text in dark mode should not be pure white. A slightly muted white looks softer and is easier to read.
- The same accent colors as in the light theme. Saturated colors that look good on a white background often become too intense on a dark one. Accents are usually lightened slightly and desaturated.
- Shadows that do not work. In a light theme we create depth with shadows. On a dark background shadows are barely visible, so hierarchy is built through differences in surface lightness.
- Images and illustrations with white backgrounds. Logos and graphics with transparent or white backgrounds can look messy. Prepare variants adapted to the dark theme.
Quick comparison of key elements
| Element | Light theme | Dark theme |
|---|---|---|
| Background | White or very light gray | Very dark gray, not pure black |
| Primary text | Dark gray | Muted white |
| Depth | Shadows | Differences in surface lightness |
| Accent | Saturated color | Slightly lightened accent |
Accessibility and contrast
Dark mode must not come at the expense of readability. The Web Content Accessibility Guidelines set minimum contrast ratios between text and background. A dark theme must meet the same standards as a light one. That means every color combination needs to be checked, not assumed to be good enough.
Pay special attention to secondary text, icons and element states such as disabled buttons. These are exactly the places where contrast is most often lost. Accessibility is not an add-on but part of quality work, which we cover in more detail through our approach to digital product development.
Conclusion
Dark mode is a valuable feature when it is well thought out, and a burden when it is added in a hurry. Start from user needs, build on semantic color tokens, respect the system preference and treat the dark theme as a design in its own right, not an inverted copy. If you are planning to add dark mode to your product or are not sure whether it is the right solution for you, we will gladly assess your case. Reach out through our contact page and we will talk through the concrete steps.

