Back to all posts
App Design7 min read·November 8, 2026

Should Your Mobile App Support Dark Mode? How to Plan It

TB
ThynkBlox Apps Team
App Engineering

For most mobile apps, supporting dark mode is worth it. Many users set their phone to a dark theme and expect apps to follow it, so an app that stays bright can feel out of place. Dark mode does have a cost, though. It works well when you plan it from the start with colour tokens, contrast checks, image rules and testing. It works badly when someone inverts the colours shortly before launch.

Should your app have dark mode at all?

Ask three questions before you commit.

  • Do your users expect it? If people use the app often, for long sessions or in low light, a dark theme is usually expected.
  • Does your brand depend on a fixed look? Some apps, such as photo editors and media players, already use a dark interface and may only need one theme. Apps built mainly around printed-style documents may decide to stay light-only.
  • Can you maintain two themes? Every new screen, illustration and component will need checking in both themes. That ongoing work belongs in your design and testing budget.

If the answers lean towards yes, plan dark mode as part of version one. Adding it to an existing app that has hard-coded colours usually means revisiting every screen.

SituationRecommendation
New app with a design system still being builtSupport light and dark from the start
Content-heavy app used for long sessionsSupport both, and follow the system setting by default
App with an intentionally dark brandOne dark theme may be enough
Existing app with colours hard-coded across screensIntroduce colour tokens first, then add dark mode
Very small prototype for idea validationDefer it, but still use tokens so it is easy to add later

How do colour tokens make dark mode manageable?

A colour token is a named role, such as "surface", "text-primary" or "border-subtle", that points to a different actual colour in each theme. Designers and developers use the role name and never the raw colour value.

Without tokens, a dark theme means hunting through every screen for each grey and white. With tokens, you define the dark values once and every component that uses them updates.

A practical starting set:

TokenPurposeLight theme ideaDark theme idea
backgroundScreen baseNear-whiteVery dark grey
surfaceCards, sheetsWhiteSlightly lighter dark grey
surface-raisedDialogs, menusWhiteLighter again
text-primaryMain textNear-blackOff-white
text-secondarySupporting textMid-greyLighter grey
borderDividers, outlinesLight greyLow-contrast grey
brand-primaryButtons, linksBrand colourAdjusted brand colour
error / success / warningStatusSaturated tonesSofter, lighter tones

The colour descriptions in this table are illustrative, not a recommended palette.

Some points to plan for:

  • Avoid pure black and pure white as the main pair. A very dark grey background with off-white text is usually more comfortable to read, and it leaves room to show depth.
  • Show elevation with lighter surfaces. Shadows are hard to see on dark backgrounds, so raised elements are usually a step lighter than the surface beneath them.
  • Adjust brand colours. A saturated brand colour that looks right on white can look harsh or lose contrast on dark grey. You may need a lighter or less saturated variant for dark mode.

Tokens are the core of a minimum design system for a mobile app. If you are setting one up, define light and dark values together.

How do you keep contrast readable in both themes?

Contrast has to pass in both themes independently. A colour pair that passes in light mode tells you nothing about its dark equivalent.

Check these pairs in each theme:

  • Primary and secondary text against background and surface.
  • Button labels against button fills, including disabled and pressed states.
  • Icons that carry meaning, such as status or navigation icons.
  • Input borders and focus indicators against their surroundings.
  • Text placed on top of images or brand colours.

Use the contrast targets in your accessibility requirements, and measure with a contrast checker instead of judging by eye. Secondary text and disabled states are where dark themes most often fail, because designers lower their contrast to look subtle and the result becomes hard to read. The mobile app accessibility design requirements guide covers contrast, text sizing and focus states in more detail.

Also avoid going too far the other way. Bright white text on a pure black background can look glaring for some readers. Off-white on dark grey usually reads better.

What should you do about images, icons and illustrations?

Images are often the part teams forget.

  • Logos and icons: Supply versions that work on dark backgrounds, or use single-colour icons that take their colour from a token.
  • Illustrations: Light illustrations with white backgrounds look like bright rectangles in dark mode. Use transparent backgrounds and either provide dark variants or choose palettes that work on both.
  • Photos and user content: Do not invert or tint them. If a large bright photo dominates a dark screen, consider a slightly darker overlay only where text sits on top of it.
  • Screenshots and diagrams inside the app: Decide whether each one needs a dark version or a contained light frame so it reads as an intentional panel.
  • Charts: Gridlines, axis labels and series colours all need dark-theme values. Check that series stay distinguishable from each other.

List every image asset during design handoff and note which ones need a dark variant. The mobile app design handoff checklist is a good place to record this.

Should users choose the theme or should the app follow the system?

Follow the system setting by default. That is what most users expect when they turn on dark mode on their phone.

Then decide whether to add an in-app choice with three options: System, Light and Dark. This helps people who want a specific app to look different from their phone. If you offer it, save the choice and apply it before the first screen draws, so the app does not flash the wrong theme on launch.

Also consider surfaces outside your main screens: the launch screen, web views, embedded payment or sign-in pages, emails opened from the app and push notification icons. A light web view inside a dark app is jarring, so check whether the content you embed can follow the theme.

How should you test dark mode?

Test dark mode as a full pass, not a quick look at the home screen.

  • Switch the system theme while the app is open and confirm every visible screen updates correctly.
  • Walk through every user flow in both themes, including loading, empty and error states. Our guide to loading, empty and error states lists the states teams often miss.
  • Test on several real devices. Screens differ in brightness and colour, and a dark grey that looks fine on one display can blend into black on another.
  • Check in bright daylight and in a dim room.
  • Run contrast checks on the built app, not only the design files.
  • Use a screen reader and larger text sizes in dark mode to catch clipped or hidden elements.
  • Include both themes in your release testing, as described in how to test an Android app before release.

Dark mode planning checklist

  • [ ] Decided whether the app supports one theme or two, and why
  • [ ] Defined colour tokens with light and dark values for every role
  • [ ] Removed hard-coded colours from components
  • [ ] Adjusted brand and status colours for dark backgrounds
  • [ ] Checked contrast for text, buttons, icons, inputs and focus states in both themes
  • [ ] Listed image assets and created dark variants where needed
  • [ ] Set system theme as default and decided on an in-app override
  • [ ] Prevented a wrong-theme flash on launch
  • [ ] Checked web views, embedded pages and the launch screen
  • [ ] Tested every flow and state in both themes on real devices
  • [ ] Added dark mode checks to the release checklist for future features

What common mistakes should you avoid?

Inverting colours automatically. Automatic inversion breaks brand colours, photos and contrast. Design the dark theme on purpose.

Using pure black everywhere. It removes your ability to show depth and can make text look glaring.

Testing only the main screens. Settings, dialogs, error messages and onboarding are where dark mode bugs usually hide.

Forgetting future work. New features shipped in light mode only slowly break the dark theme. Make both themes part of the definition of done.

Lowering contrast to look elegant. Subtle grey-on-grey text often fails readability checks.

When does this not apply?

If your app is a short-lived prototype built to validate an idea, a second theme can wait. Use colour tokens anyway so adding it later is a small change. If your product is designed around one fixed dark or light look, a single well-tested theme can be the right call. Just make that a deliberate decision and explain it in your design notes.

What questions do founders often ask?

Does dark mode add a lot to development cost?

It adds design and testing effort, mostly in defining tokens, creating asset variants and testing both themes. The cost is much lower when you plan it from the start than when you add it to an app with hard-coded colours.

Can we launch without dark mode and add it later?

Yes, if you build with colour tokens from day one. Without tokens, adding it later usually means reworking many screens.

Do iOS and Android handle dark mode differently?

Both platforms let users choose a system theme, and both let apps respond to it. The details of how each platform applies the theme differ, so confirm the approach with your developers, especially for cross-platform builds.

Does dark mode save battery?

Any effect depends on the device's screen and on what the app shows, so do not promise battery savings. Treat it as a user preference feature, not a battery feature.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.