Dark mode

During validation research on minor background colour changes (Beige to Grey), users spontaneously requested dark mode for the DataCamp learning platform. This request strongly aligns with the common pattern for developers to use dark screen IDEs when coding. The main reason for this is eye strain, which tends to be worse early
and late in the day — a typical time for learners to complete courses.

Using this data, we proposed building and rolling out dark mode across the experience. In addition, in order to future-proof the application, I decided that we should approach dark mode as a system of theming rather than a bespoke colour design for each component. This would make the process somewhat simpler, retain the design contrast ratios and accessibility, and equally allow for any future themes, e.g. high contrast for visually impaired users, or custom themes for enterprise customers who wished to create a branded experience.

A big part of this project was fixing the previous attempts at dark mode. These had been designed at a component level rather than creating a system-level theme. Step 1 was to fix this issue and create a theme-based approach. This was also then extensible for future new themes, e.g. accessible high contrast, but equally some customers desired brand-coded experiences for their own LMS systems.

Going Dark

Dark mode was an important strategic initiative based on a few key considerations. Firstly, higher conversions versus more developer-friendly platforms like Replit. We also created a hybrid mixed mode combining both dark and light modes.

What the TAM?

The company was operating in a somewhat saturated vertical of data science skills. This segment represents a sub-10% fraction of the full developer market. My proposal was to broaden the scope to cover the full developer audience, increasing the potential target market by 10×. Part of making this shift to broader engineering-focused courses was to bring in dark mode for the full experience.