Push Notifications: Best Practice and Pitfalls
Push notifications are messages your app can send to a user's device even when the app is closed. Used well, they bring people back and add genuine value; used badly, they are the fastest way to get your app deleted.
The difference comes down to relevance, timing and respect for the user's attention.
Permission Comes First
Before you can send a single notification, the user has to grant permission, and on most platforms they only get asked once. Squander that moment and you may never get another chance. We therefore explain the benefit in plain terms first, ask at a point where the value is obvious, and give people clear controls afterwards so they can fine-tune what they receive rather than turning everything off.
When Notifications Help
- Time-sensitive updates the user actually asked for.
- Confirmations and status changes, such as an order dispatched.
- Genuinely personal reminders tied to the user's own activity.
Common Pitfalls
- Sending too often until people switch them off.
- Generic marketing blasts with no personal relevance.
- Asking for permission before explaining the benefit.
How We Set Them Up
We ask for notification permission at a sensible moment — after the user sees the value — and give people granular control over what they receive. Quiet, relevant notifications keep opt-in rates high.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.