App dark mode: design and support basics

The short answer

App dark mode means your app follows the phone's dark appearance setting. Apple and Google both advise following the system setting by default and using named theme colours instead of fixed ones. You do not strictly have to support it, but an app that stays light when the phone is dark can feel jarring, so decide early.

What app dark mode actually is

App dark mode is the app's response to a setting the user chose on the phone. When the phone is set to a dark appearance, the app shows light text on dark surfaces. When it is set to light, the app shows the reverse. The user does not toggle it inside your app unless you add that option.

It is not a second logo or a second brand. It is the same interface drawn with a second set of colours. That is why it is a design-system decision more than a feature. If your colours are scattered through the code as fixed values, supporting dark mode later means touching every screen. If they are defined once as roles, such as "background", "primary text" and "divider", the second theme is mostly a second set of values.

Do I need to support dark mode?

Neither store forces you to. But Apple's design guidance says apps should follow the system appearance, and keeps always-dark for a small group such as media and creative apps. Android's developer documentation likewise recommends following the system setting as the default, and offers light, dark and system choices inside the app as an option.

For most business apps the practical answer is yes, eventually. People who use dark mode notice a bright white screen, especially at night. The question is when, not whether.

• If you are building a first version, design with colour roles from the start. It costs little then and a lot later.
• If you are launching under time pressure, you can ship light only and plan dark mode for the first update. Say so in your plan so it does not drift.
• If the app is mostly photos or video, check that your overlays and text stay readable on both themes.

The first version of your app does not need every feature, but the colour system is easier to build once.

Dark mode design is not an inverted light mode

Both Apple and Google warn against simply inverting colours. A pure inversion turns shadows into glows, makes brand colours garish and flips images that should not flip. Design the dark theme on its own terms.

• Use dark grey or very dark colour for backgrounds rather than pure black unless you have a reason. Check how it sits next to your content.
• Raise surfaces, such as cards and sheets, by making them slightly lighter than the background. In dark themes, lightness replaces shadow as the way to show depth.
• Soften large areas of saturated colour. A brand colour that works as a small accent on white can glare as a large fill on dark.
• Keep text contrast readable. The accessibility basics in mobile app accessibility basics apply to both themes.

Android's documentation also advises against relying on a quick automatic fallback that darkens a light app. It exists, but the platform says building a proper dark theme gives better results and more control.

What breaks first when dark mode is added

The same things go wrong in almost every app. Knowing them lets you search for them before a user finds them.

Transparent logos in dark artwork are a common source of trouble. A dark logo on a dark surface disappears. Ask your designer for a version that works on both, or a separate light-on-dark variant. The same thinking applies to the first screens people see; the guide on designing app onboarding is a good place to check both themes first.

How to test light and dark themes

Test every screen in both themes, in both orientations if the app supports them, and at large text sizes. That sounds like a lot, so structure it.

1. List every screen and state, including errors, empty lists and loading.
2. Go through the list once in light and once in dark, on a real device and in a simulator or emulator.
3. Switch themes while the app is open. Some screens only read the theme on launch and stay wrong until restarted.
4. Check pop-ups, sheets, alerts, date pickers and the keyboard, since they come from the system and can clash with custom colours.
5. Take screenshots of both themes side by side and look for the odd one out.

Add the two themes to your release checklist. The general testing steps are in how to test a mobile app before launch, and dark mode fits in as one more dimension, alongside devices and system versions.

Dark mode, store review and other effects

An app is not rejected for lacking dark mode. But an app that shows unreadable text in one theme can look broken to a reviewer, and broken apps can be refused. The wider list of reasons is in why apps get rejected from app stores.

Other parts of your product also appear on dark screens. Many mail apps show emails in dark mode, and notification images sit on whatever the lock screen is. If you are choosing between channels for a message, think about how each looks. That choice is explored in push notifications, email and SMS compared.

Dark mode can also be a small performance factor on some screens, but the effect depends on the device, and we would not make it the reason to build it. The basics of speed are in app performance basics.

A sensible order of work

If you are adding dark mode to an existing app, do it in a fixed order so it does not stall.

1. Agree a short list of colour roles with the designer.
2. Replace fixed colours in shared components first, since they affect every screen.
3. Fix images and logos that carry a background.
4. Go screen by screen, starting with the most visited.
5. Test, then ship, and write the change into the update notes.

If you want a team to plan this with you, the mobile app development service page explains what Liftup Technologies builds. The decision on whether to do it now or later depends on your budget, platform and timeline, and we would rather say that plainly than promise a fixed route.

Related guides

• Mobile app development
• App onboarding how to design the first screens
• How to test a mobile app before launch
• Push vs Email vs SMS: Which Channel for Which Message
• App Performance: Launch Time, Memory and Battery Basics
• App localisation basics

Questions and answers

Do I need to support dark mode in my app?

Neither store requires it. Apple and Google both advise following the system appearance by default, and many users keep dark mode on. If you ship light only, plan dark mode for an early update.

What breaks first when dark mode is added?

Invisible text, logos and images with white backgrounds, fixed colours in custom components, web views and system elements such as the keyboard. Searching for fixed colour values early finds most of them.

How do I test both themes?

List every screen and state, then go through the list once in each theme on a real device. Switch themes while the app is open, because some screens only read the theme at launch.

Is dark mode just inverted colours?

No. Apple and Google both advise against simple inversion. Dark themes need their own surface levels, softened brand colours and checked text contrast.

Should users be able to choose a theme inside the app?

It is optional. Android's documentation lists light, dark and system default as common options, with the system setting as the recommended default. Following the system setting is enough for most apps.