Getting started with push notifications
The gap between knowing this and actually doing it is where most teams lose ground. A short on-ramp to push notifications for teams who have not touched it before.
You do not control the device, the network, or the operating system version, and the design has to accept that. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.
Why this earns attention
Permission is granted once and revoked forever. In practice this is a scheduling problem more than a technical one. Budget a little time for it every quarter and it never becomes a project of its own.
Your first week
- Find out what is already in place
- Notify about things people asked for, not things you want to say
- Change one thing and measure it
Deep link into the exact screen the notification is about. None of that requires a large budget, only a decision and someone to own it. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.
In practice
The version of the app your customers are running is rarely the one you just shipped. Three things worth confirming about push notifications before you move on:
- Someone can say what the current setup is without going to look
- Deep link into the exact screen the notification is about — and you know whether that is true here
- There is a way to tell whether the last change to this helped
Most of the value here comes from doing the first two things, not all of them.