Dark Mode Switch
Dark Mode changes the appearance of OneNote interface elements from light to dark, which can improve readability in low light environments, increase the legibility of the user interface as well as your notes, and provide better contrast. Dark Mode doesn’t actually alter the properties of your page content in any way. 🌓Dark Mode Switch. Add a dark-mode theme toggle with a Bootstrap Custom Switch. Uses local storage to save preference; Only 262 Bytes minified and gzipped!
Take the pain out of building site search with the Algolia hosted API. Start free now!
I like when websites have a dark mode option. Dark mode makes web pages easier for me to read and helps my eyes feel more relaxed. Many websites, including YouTube and Twitter, have implemented it already, and we’re starting to see it trickle onto many other sites as well.
In this tutorial, we’re going to build a toggle that allows users to switch between light and dark modes, using a <ThemeProvider
wrapper from the styled-components library. We’ll create a useDarkMode
custom hook, which supports the prefers-color-scheme
media query to set the mode according to the user’s OS color scheme settings.
If that sounds hard, I promise it’s not! Let’s dig in and make it happen.
See the Pen
Day/night mode switch toggle with React and ThemeProvider by Maks Akymenko (@maximakymenko)
on CodePen.
Let’s set things up
We’ll use create-react-app to initiate a new project:
Next, open a separate terminal window and install styled-components:
Next thing to do is create two files. The first is global.js
, which will contain our base styling, and the second is theme.js
, which will include variables for our dark and light themes:
Feel free to customize variables any way you want, because this code is used just for demonstration purposes.
Go to the App.js file. We’re going to delete everything in there and add the layout for our app. Here’s what I did:
This imports our light and dark themes. The ThemeProvider
component also gets imported and is passed the light theme (lightTheme
) styles inside. We also import GlobalStyles
to tighten everything up in one place.
Here’s roughly what we have so far:
Now, the toggling functionality
There is no magic switching between themes yet, so let’s implement toggling functionality. We are only going to need a couple lines of code to make it work.
First, import the useState
hook from react
:
Next, use the hook to create a local state which will keep track of the current theme and add a function to switch between themes on click:
After that, all that’s left is to pass this function to our button element and conditionally change the theme. Take a look:
How does it work?
Earlier in our GlobalStyles
, we assigned background
and color
properties to values from the theme
object, so now, every time we switch the toggle, values change depending on the darkTheme
and lightTheme
objects that we are passing to ThemeProvider
. The transition
property allows us to make this change a little more smoothly than working with keyframe animations.
Now we need the toggle component
We’re generally done here because you now know how to create toggling functionality. However, we can always do better, so let’s improve the app by creating a custom Toggle
component and make our switch functionality reusable. That’s one of the key benefits to making this in React, right?
We’ll keep everything inside one file for simplicity’s sake, so let’s create a new one called Toggle.js
and add the following:
You can download icons from here and here. Also, if we want to use icons as components, remember about importing them as React components.
We passed two props inside: the theme
will provide the current theme (light or dark) and toggleTheme
function will be used to switch between them. Below we created an isLight
variable, which will return a boolean value depending on our current theme. We’ll pass it later to our styled component.
We’ve also imported a styled
function from styled-components, so let’s use it. Feel free to add this on top your file after the imports or create a dedicated file for that (e.g. Toggle.styled.js) like I have below. Again, this is purely for presentation purposes, so you can style your component as you see fit.
Importing icons as components allows us to directly change the styles of the SVG icons. We’re checking if the lightTheme
is an active one, and if so, we move the appropriate icon out of the visible area — sort of like the moon going away when it’s daytime and vice versa.
Don’t forget to replace the button with the ToggleContainer
component in Toggle.js, regardless of whether you’re styling in separate file or directly in Toggle.js. Be sure to pass the isLight
variable to it to specify the current theme. I called the prop lightTheme
so it would clearly reflect its purpose.
The last thing to do is import our component inside App.js and pass required props to it. Also, to add a bit more interactivity, I’ve passed condition to toggle between “light” and “dark” in the heading when the theme changes:
Don’t forget to credit the flaticon.com authors for the providing the icons.
Now that’s better:
The useDarkMode hook
While building an application, we should keep in mind that the app must be scalable, meaning, reusable, so we can use in it many places, or even different projects.
That is why it would be great if we move our toggle functionality to a separate place — so, why not to create a dedicated account hook for that?
Let’s create a new file called useDarkMode.js in the project src
directory and move our logic into this file with some tweaks:
We’ve added a couple of things here. We want our theme to persist between sessions in the browser, so if someone has chosen a dark theme, that’s what they’ll get on the next visit to the app. That’s a huge UX improvement. For this reasons we use localStorage
.
We’ve also implemented the useEffect
hook to check on component mounting. If the user has previously selected a theme, we will pass it to our setTheme
function. In the end, we will return our theme
, which contains the chosen theme
and toggleTheme
function to switch between modes.
Now, let’s implement the useDarkMode
hook. Go into App.js, import the newly created hook, destructure our theme
and toggleTheme
properties from the hook, and, put them where they belong:
This almost works almost perfectly, but there is one small thing we can do to make our experience better. Switch to dark theme and reload the page. Do you see that the sun icon loads before the moon icon for a brief moment?
That happens because our useState
hook initiates the light
theme initially. After that, useEffect
runs, checks localStorage
and only then sets the theme
to dark
.
So far, I found two solutions. The first is to check if there is a value in localStorage
in our useState
:
However, I am not sure if it’s a good practice to do checks like that inside useState
, so let me show you a second solution, that I’m using.
This one will be a bit more complicated. We will create another state and call it componentMounted
. Then, inside the useEffect
hook, where we check our localTheme
, we’ll add an else
statement, and if there is no theme
in localStorage
, we’ll add it. After that, we’ll set setComponentMounted
to true
. In the end, we add componentMounted
to our return statement.
You might have noticed that we’ve got some pieces of code that are repeated. We always try to follow the DRY principle while writing the code, and right here we’ve got a chance to use it. We can create a separate function that will set our state and pass theme
to the localStorage
. I believe, that the best name for it will be setTheme
, but we’ve already used it, so let’s call it setMode
:
With this function in place, we can refactor our useDarkMode.js a little:
We’ve only changed code a little, but it looks so much better and is easier to read and understand!
Did the component mount?
Getting back to componentMounted
property. We will use it to check if our component has mounted because this is what happens in useEffect
hook.
If it hasn’t happened yet, we will render an empty div:
Here is how complete code for the App.js:
Using the user’s preferred color scheme
This part is not required, but it will let you achieve even better user experience. This media feature is used to detect if the user has requested the page to use a light or dark color theme based on the settings in their OS. For example, if a user’s default color scheme on a phone or laptop is set to dark, your website will change its color scheme accordingly to it. It’s worth noting that this media query is still a work in progress and is included in the Media Queries Level 5 specification, which is in Editor’s Draft.
This browser support data is from Caniuse, which has more detail. A number indicates that browser supports the feature at that version and up.
Mobile / Tablet
Android Chrome | Android Firefox | Android | iOS Safari |
---|---|---|---|
90 | 87 | 90 | 13.0-13.1 |
The implementation is pretty straightforward. Because we’re working with a media query, we need to check if the browser supports it in the useEffect
hook and set appropriate theme. To do that, we’ll use window.matchMedia
to check if it exists and whether dark mode is supported. We also need to remember about the localTheme
because, if it’s available, we don’t want to overwrite it with the dark value unless, of course, the value is set to light.
If all checks are passed, we will set the dark theme.
As mentioned before, we need to remember about the existence of localTheme
— that’s why we need to implement our previous logic where we’ve checked for it.
Here’s what we had from before:
Let’s mix it up. I’ve replaced the if and else statements with ternary operators to make things a little more readable as well:
Here’s the userDarkMode.js file with the complete code:
Give it a try! It changes the mode, persists the theme in localStorage
, and also sets the default theme accordingly to the OS color scheme if it’s available.
Dark Mode Switch Chrome
Congratulations, my friend! Great job! If you have any questions about implementation, feel free to send me a message!