Dark mode testing checklist for iOS and Android apps
To test dark mode on iOS and Android, run the same critical task from launch in light and dark appearance. Then switch appearance in both directions with the task still in progress. Check that you can read the screen, finish the task and keep any work the app is meant to preserve.
Which appearance changes should you test?
In a fictional expenses app, open a new claim, enter an amount and attach a test receipt. Leave the form open with the claim unsaved before each mid-task switch.
For a manual switch, use the Dark Mode control in iPhone Control Centre or the Dark theme tile in Android Quick Settings if it's available. Change the setting without closing the app, then return to the form. Apple's Dark Mode controls, Android's dark theme controls.
| Test case | What to check |
|---|---|
| Launch in Light and launch in Dark | Set the phone's appearance before each launch. Watch for a flash of the opposite colour, then open the same task in each run. |
| Switch from Light to Dark mid-task | Return to the same screen. Check the amount and receipt are still there, then finish the claim. |
| Switch from Dark to Light mid-task | Use a new claim. Check that icons, labels and validation messages update on the screen that's already open. |
| Change appearance while the app is in the background | Return through the app switcher. Check that the visible screen reflects the new setting and that you can continue. |
| Set an in-app appearance if the app provides one | Set the app to Dark while the phone is in Light. Close and reopen to check that the app keeps its setting. If the app has a System option, select it and switch the phone's appearance again. |
If the iOS app follows the system, set a custom appearance schedule for a few minutes ahead and leave the claim open through the switch. On Android, a theme change can recreate the activity for the current screen. Check that the form stays on the same step with its values intact. Apple's Dark Mode guidance, Android's dark theme guide.
Which parts of a screen need a closer look?
Try submitting with the amount blank. Can you read the error and see which field needs fixing? Repeat in both appearances, then check the parts of the task a screenshot of the loaded form would miss.
- Loading and empty states. Open a claim with no receipts, then load a receipt preview. Check the empty-state hint and wait indicator against their backgrounds.
- Images and overlays. Open the receipt preview and find its close button. Check the status bar icons against the preview and make sure you can dismiss it.
- Embedded content. If a help or payment page opens inside the app, read it and try its controls. Check the edges where the embedded page meets the app, then return to the claim.
On iOS, rerun the hardest-to-read screen with Increase Contrast and Reduce Transparency enabled separately and together. A label that reads well on the default translucent sheet can be hard to read when its background changes. Apple's Dark Mode guidance.
What should a dark mode bug report include?
Write down how you reached the broken screen before you restart the app. An issue titled “Receipt preview close icon disappears after switching from Light to Dark” tells the next person which screen to leave open and which way to switch. Record whether the same failure appears when you launch directly in Dark appearance.
Screen and task
Device, OS and app build
Phone appearance before and after
In-app appearance setting, if present
How you switched and whether the app was already open
Expected behaviour
Actual behaviour and effect on the task
Result after launching directly in the destination appearance
Screenshot or recording, with timestamp if relevant
Use test data in the evidence. For the missing close icon, capture the same screen before and after the switch so the difference is visible. If the screen flashes white and then settles, record the switch itself and note the timestamp. How to record a mobile bug.
When you file the issue, paste the appearance settings into the reproduction steps so they travel with the ticket. Open the bug report template generator.
Frequently asked questions
Do I need to test dark mode on a physical phone?
Use a simulator or emulator to run through both appearances and repeat theme switches. Before release, check a physical phone on each supported platform for the priority flows, especially if the issue involves system UI, a brief flash or a setting specific to that model. Record the device and operating system you used.
What if the app has its own theme setting?
Test each option the app offers. For a System option, change the phone's appearance and verify that the app follows it. If the app offers explicit Light and Dark choices, verify that each behaves as specified when the phone's setting changes and after reopening the app.
What should I attach to a dark mode bug report?
Attach a screenshot for a lasting problem, such as a missing icon. Use a short screen recording for a flash or a failure during a switch. Include the device, OS, build, system appearance, any in-app override and the action that made the problem visible.