Notification settings are a promise about control. This list checks that what the user switches matches what arrives, on a real device. You need a way to trigger each notification type, such as a test button, a staging backend or a push console.
The checklist
- Permission is requested at a good moment. - Why: asking at first launch with no context gets denied. - How to check: fresh install. The system prompt appears after the user understands the value, not before, and your own explanation matches it.
- Denied permission is handled. - Why: many users deny. The app must still work. - How to check: deny. The app works, settings show that notifications are off at system level and link to system settings.
- Each notification type can be controlled. - Why: one all-or-nothing switch makes people turn everything off. - How to check: list every type you send (messages, reminders, offers). Each has a clear name and its own switch, or you made a conscious decision not to.
- Switch off means nothing arrives. - Why: this is the key promise. - How to check: turn a type off, trigger it, wait. Nothing arrives, on that device and on others signed in to the account.
- Switch on means it arrives. - Why: the opposite bug is just as common. - How to check: turn it on again, trigger, confirm arrival within a reasonable time with correct text.
- Defaults are explicit. - Why: marketing types on by default surprise people. - How to check: on a fresh account read which types are on. Decide whether each default is what a user expects.
- Channels on Android. - Why: users control importance, sound and vibration per channel in system settings. - How to check: open the app's notification settings in Android. Channel names and descriptions are understandable and match your in-app settings. Change a channel's sound and importance; the next notification follows.
- Quiet hours or do-not-disturb. - Why: a night-time ping is the fastest route to uninstall. - How to check: set quiet times in the app, trigger a notification inside and outside the window. Check time zones: change the device zone and a daylight-saving boundary if you can. Also test the system Do Not Disturb or focus mode.
- Opt-out via the notification itself and via email. - Why: users look for the way out where they get the message. - How to check: if a notification or email has an unsubscribe or settings link, it opens the right screen and works.
- Settings sync across devices.
- Why: preferences should follow the account if you say so.
- How to check: change on device A, trigger, and check device B behaves as designed.
- Notification content.
- Why: lock-screen text can leak private information.
- How to check: view notifications on the lock screen. Sensitive content is hidden or minimal, as designed. Long text truncates well.
- Tapping leads to the right place.
- Why: a notification that opens the home screen wastes the click.
- How to check: tap each type while the app is closed, in the background and open. Each lands on the relevant screen, also when signed out.
- Grouping, badge counts and clearing.
- Why: a badge that never clears feels broken.
- How to check: receive several, read them in the app, check badge count and that the delivered notifications are removed.
- Behavior after reinstall or sign-out.
- Why: tokens go stale; notifications for a signed-out user are a privacy problem.
- How to check: sign out and trigger a notification for that account: nothing arrives. Reinstall and sign in: delivery resumes.
- Account deletion and notifications.
- Why: no notification should arrive after deletion.
- How to check: after the account deletion flow, trigger a notification. Nothing arrives.
- Wording in settings.
- Why: unclear labels cause wrong choices.
- How to check: read each label and description in all languages; say what the user gets, not the technical name.
Related
Back to all checklists · Image upload checklist · Chat and messaging checklist
Do your notification settings feel obvious to someone new? Start free: private, structured feedback, 1 feedback = 1 credit.