ShouldStartupFoundersDefaulttoDarkModefortheirSaaSProduct?

Dark mode isn't just a trend; it's a significant shift in how people interact with digital products. A study by the Nielsen Norman Group found that 82% of mobile users have adopted dark mode. That's not a niche preference—that's mainstream adoption.

So why is dark mode becoming so popular, and what does it mean for those of us creating new products?

One reason is reduced eye strain. Screens emit blue light, which can cause fatigue and disrupt sleep patterns. Dark mode minimises blue light exposure, especially in low-light conditions. Users who spend long hours staring at screens—think developers, designers, or anyone glued to their devices—find dark mode less taxing on the eyes.

There's also the matter of battery life. On devices with OLED or AMOLED screens, dark mode can significantly extend battery performance. A Purdue University study found that switching to dark mode could save up to 47% of battery power at average brightness levels. Considering no one is interested in adding larger batteries to phones, this is the next best thing.

But beyond the practical advantages, dark mode has an aesthetic appeal. It offers a sleek, modern look that many users prefer. Companies like Spotify have embraced dark mode as their default, creating an immersive experience where the interface fades into the background, allowing the content to shine. It's like walking into a dimly lit room where your focus naturally gravitates toward what's important.

Given these benefits, it seems logical for designers and developers to adopt a "dark first" approach. But it's not that simple. The decision to prioritise dark mode depends on several factors, including the target market and the nature of the product. (Although several of our clients just like the aesthetic).

What industries or customers prefer dark mode?

Let's talk about target markets where going dark first makes sense. If you're building products for tech-savvy users—developers, designers, gamers—dark mode should be high on your list.

These users often prefer dark interfaces because they align with their workflows and environments. Tools like Slack, GitHub, and various code editors offer robust dark mode options, catering to this audience's preferences.

Media consumption platforms are another area where dark mode excels. Apps like Netflix, YouTube, and Kindle use dark backgrounds to enhance the viewing and reading experience. The focus is on the content, not the interface, which is precisely what users want when immersing themselves in a movie or a book.

Then there are productivity tools. Software that involves prolonged screen time can benefit from a dark interface. Users working late hours or in dimly lit environments appreciate the reduced glare. Offering a dark mode can make your product more appealing to these users.

However, not all industries are on the dark mode bandwagon. Legacy sectors like finance, healthcare, and legal services often stick to light mode, and for good reasons. These industries prioritise clarity, professionalism, and tradition.

When is not a good idea to build in dark mode?

Take finance and banking apps, for instance. They use light interfaces to convey transparency and trustworthiness. The clean, bright design aligns with their brand identity and the serious nature of financial transactions. A dark interface might seem out of place or even unsettling to their user base.

Healthcare applications also lean toward light mode. When dealing with critical health information, clarity is paramount. A light background with dark text ensures maximum readability, reducing the risk of misinterpretation. In such contexts, the benefits of dark mode don't outweigh the need for precision and clarity.

Educational platforms and e-learning tools often prefer light interfaces as well. Studies have shown that light mode aids comprehension and retention during daytime use. When the goal is to facilitate learning, sticking with what's proven to work makes sense.

So, if you're developing products for these industries, a light-first approach might be more appropriate. It's not about resisting change but about understanding the needs and expectations of your users.

How to implement a dark mode?

Implementing dark mode isn't just a matter of inverting colours. It presents unique design challenges. On dark backgrounds, the range of usable colours is reduced. Saturated colours can cause visual vibration, making elements hard to look at. Ensuring sufficient contrast for readability becomes more complex. Designers need to rethink visual hierarchy, depth, and how components like forms and tables appear.

There's also the issue of brand identity. Adapting a brand's colour scheme to work in dark mode can be tricky, especially if the original palette relies on bright or light colours. Consistency across platforms adds another layer of complexity. Some devices or operating systems might not fully support dark mode, leading to a fragmented user experience.

From a development standpoint, supporting both light and dark modes can double the work. Every component and interaction needs to be tested in both modes to ensure functionality and aesthetics remain intact.

When working with Antler this has implications for timelines and budgets (although there are ways to manage it and make it closer to 1.1/1.2x the frontend work costs). Clients need to understand that implementing dark mode isn't a trivial addition; it's a reasonable extra cost investment.

So, where does this leave us? Should we default to dark mode, stick with light mode, or offer both?

I think the answer lies in understanding our users and the context in which they use our products. If we're building for markets favouring dark mode, prioritising it makes sense. For others, light mode remains the sensible default.

Obviously, if you can afford the extra cost, the best approach is flexibility. Suppose you're a new company without a strong brand. In that case, you can tailor your brand to fit both light and dark, making the implementation easier.

Offering users the choice between dark and light modes caters to individual preferences. Some users switch modes based on the time of day or their environment.

Of course, this requires more effort during design and development. However, it might be worth the investment in a world where user experience is a key differentiator. It's about meeting users where they are rather than forcing them into a one-size-fits-all solution.

Should you include dark mode?

As entrepreneurs and product builders, we need to stay attuned to these shifts. The rise of dark mode isn't just a design trend; it's a reflection of changing user expectations. People want interfaces that adapt to them, not the other way around.

Just because 82% of mobile users have adopted dark mode doesn't mean it's the right choice for every product. Usability and content clarity should always take precedence over following the crowd.

Of course, there is a reasonable argument that dark mode is purely about saving battery on mobile devices. Otherwise, we would see a similar number of desktops opting for dark mode as the default.

So, should we be "dark first" when designing new products? For some markets, absolutely. For others, perhaps not. The key is to understand who we're designing and building for and why.

Even if the decision doesn't opt for a dark mode in the first iteration of the product, we often advise clients to allow it to be set up so that in the future, we can implement it for a much lower cost. If you don't set the project up for dark mode at the start, then adding it later can be a significant expense.