OOmnistu

Blog / Mobile App Development

Mobile App Development

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.

OOmnistu
Reviewed 2026-11-19 · 3 min read

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:

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

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.