Reaching users outside the application.
HOW THEY WORK
Your server sends a message to the platform's service, which delivers it to the device.
WHAT YOU NEED
Platform credentials A device token per installation, registered with your server Handling for tokens that change or expire
WHY TOKENS CHANGE
Reinstallation, restoration to a new device, and periodic refresh.
WHAT TO DO
Refresh and re-register regularly, and remove tokens that are rejected.
WHAT PERMISSION IS REQUIRED
Explicit permission on both platforms now.
WHEN TO ASK
After demonstrating why they are useful, not on first launch.
WHY
Refused permission is difficult to recover.
WHAT TO SEND
Notifications the user actually wants.
WHAT TO AVOID
Marketing disguised as alerts High frequency Notifications with no action Sending at unsocial hours without considering time zones
WHAT USERS DO IN RESPONSE
Disable notifications entirely, or uninstall.
WHAT TO PROVIDE
Granular settings, so they can disable categories rather than everything.
WHAT TO HANDLE
A notification opening a specific screen, with a sensible history.
WHAT TO NEVER INCLUDE
Sensitive content, which appears on a locked screen.
