Dark mode done right: follow the system, skip your own toggle
Apple's HIG says avoid an app-specific appearance setting; Android's DayNight themes do the heavy lifting. Semantic colors, values-night resources, and the accessibility-settings test pass most teams skip.
Dark mode is no longer a nice-to-have toggle. On iOS, iPadOS, macOS and tvOS, users often choose Dark Mode as their default interface style and generally expect every app to respect it; Android offers the same systemwide choice. Shipping an app that ignores the setting reads as broken to exactly the users who care most. The good news: both platforms do most of the work if you build on their theme systems instead of hard-coding colors.
What Apple expects
Apple's Human Interface Guidelines are unusually direct on three points:
- Do not add your own appearance setting. An app-specific light/dark toggle makes users configure the same thing twice, and if the app stops responding to the systemwide choice users may think it is broken. Follow the system.
- Support both appearances, including automatic switching. People can set appearance to Auto, which flips between light and dark as conditions change through the day - potentially while your app is on screen. Your app must handle the transition live, not just on next launch.
- Test legibility with accessibility settings on. Apple calls out Dark Mode combined with Increase Contrast and Reduce Transparency as the combination where dark text on dark backgrounds quietly becomes illegible for many users.
On colors: the dark palette is not a mechanical inversion of the light one - many colors invert, some do not. Apple's answer is semantic colors (such as labelColor on macOS or separator on iOS) that adapt automatically, and Color Set assets in the Xcode asset catalog with bright and dim variants for anything custom. Hard-coded hex values are the thing to avoid. A permanently dark interface is acceptable only in rare cases, such as immersive media viewing where a receding UI helps focus.
What Android gives you
On Android the foundation is a DayNight theme. Inherit your app theme from Theme.AppCompat.DayNight or the Material Components equivalent (Theme.MaterialComponents.DayNight, typically in res/values/styles.xml), and provide dark resources in values-night. The system then switches your app with the device setting, and AppCompatDelegate can recreate running activities when the mode changes.
For a fast first pass, Android 10 added Force Dark: the system analyzes each view of a light-themed app and draws a dark version automatically. It is explicitly a way to implement a dark theme quickly without a full DayNight setup, and it shows. Treat Force Dark as a triage tool - enable it, walk every screen, then replace the worst results with real values-night resources and opted-out views. A hand-tuned dark theme reads better and avoids the inverted-brand-color accidents Force Dark can produce.
Design rules that apply on both
- Do not use pure black backgrounds by default. Dark gray surfaces keep elevation shadows visible and reduce smearing on OLED screens.
- Recheck contrast, not just hue. Body text needs enough contrast against its dark surface in every appearance; system colors get you most of the way, custom brand colors are where failures hide.
- Audit images and illustrations. Art designed for a white background can carry baked-in light edges or invisible-on-dark line work. Provide dark variants where it matters, starting with onboarding and empty states.
- Test the transitions. Toggle the system appearance with the app open, with Auto enabled overnight, and with Increase Contrast and Reduce Transparency on iOS. Each of those finds a different class of bug.
The pragmatic path
Adopt the platform theme system (semantic colors on Apple platforms, a DayNight theme on Android), enable Force Dark only as an interim measure, run the accessibility-settings pass, and audit your top ten screens by eye. Most teams get a credible dark mode in days once they stop maintaining their own toggle.
Sources
Prepared with AI assistance and reviewed before publication. Platform guidance quoted and paraphrased from Apple's and Google's documentation, checked on 19 November 2026.