A setting is a promise: "I change this and it stays changed." Test each setting one by one. Keep a table with the columns setting, default, changed value, effect, survives restart.
The checklist
- Every setting has a sensible default. - Why: most users never open settings. - How to check: fresh install, no changes. The app behaves well, and every toggle shows its real state.
- The setting has an immediate effect. - Why: a toggle that does nothing erodes trust. - How to check: change it and go to the screen it affects. The effect is visible without a restart, unless the app says a restart is needed.
- It survives closing the app. - Why: persistence is the core promise. - How to check: change it, swipe the app away, reopen. The value and effect are unchanged.
- It survives a device restart. - Why: some storage is cleared or reset on reboot if done wrong. - How to check: change it, reboot the phone, open the app.
- It survives an app update. - Why: updates and migrations can reset preferences. - How to check: install an older build, change settings, update to the new build over it. Values are kept. See testing updates.
- It survives sign-out and sign-in. - Why: is the setting per device or per account? Users have an expectation. - How to check: change, sign out, sign in as the same user, then as another. Match your intended design: account settings follow the account, device settings stay.
- Reset to defaults works and is safe. - Why: a reset must not wipe data by surprise. - How to check: use reset. A confirmation says what is reset, only settings go back, user data stays.
- Dependent settings. - Why: one option can make another meaningless. - How to check: turn off a parent option. Child options are disabled or hidden with a reason, and their values come back when re-enabled.
- Language, region and theme. - Why: these change every screen. - How to check: switch each, also while screens are open. Text, formats and colors update everywhere, including dialogs and notifications. Check dark mode contrast.
- Text size and accessibility options.
- Why: in-app and system settings can fight each other.
- How to check: set the largest system font size and bold text; settings labels do not truncate.
- Changes while offline.
- Why: synced settings need a plan when there is no network.
- How to check: change a synced setting in airplane mode. Either it is saved and synced later, or the user is told. See the error states checklist.
- Two devices.
- Why: synced settings can conflict.
- How to check: change the same setting on two devices; the result is predictable (latest wins) and consistent after sync.
- System-level conflicts.
- Why: a setting may say "on" while the OS permission is off.
- How to check: enable an in-app option, then revoke the OS permission. The app shows the real state and a way to fix it.
- Links and info texts inside settings.
- Why: privacy, terms, help and version entries are often dead.
- How to check: tap each. They open, the version number is correct, and back returns to settings.
- Wording.
- Why: "Enable disabling of..." confuses.
- How to check: read each label and description. A toggle's text says what happens when it is on.
Related
Back to all checklists · Account deletion checklist · Consent and privacy checklist
Want someone to flip every switch and report what did not stick? Start free: private, structured feedback, 1 feedback = 1 credit.