Push Notifications

A push notification is a short message that lands on someone's phone or browser without them opening your app, which is why they have to give permission first.

Also known as push message app notification browser notification

Definition

A push notification is a short message that appears on a phone or a computer screen while the person is busy with something else. They never open your app or your website to see it, because the phone puts it in front of them. It is usually one line of text, sometimes a small picture, and a tap that opens the right page.

Only a business the person has agreed to hear from can send one, so the phone or the browser asks first with a small box. The answer is yes or no, and a no means nothing you build later can reach them. That box appears once, so the moment you ask matters more than the wording. Most refusals come from asking on the very first screen, before anyone knows what the app does. Ask after the first booking and far more people say yes.

The messages worth sending are the useful ones, the sort that save the reader a phone call. Your class starts in an hour, your order has left the warehouse, or the dentist has moved your Tuesday appointment to Wednesday. Nadiva sends salon and gym reminders exactly like these, and a chair that would have sat empty gets filled.

iPhones carry one rule that catches people out, because a website can only reach an iPhone if the customer adds it to the home screen first. Hardly anyone does that, so if your customers carry iPhones you need a real app from the App Store. Android phones and desktop browsers are easier, but even there nothing is guaranteed. A phone that is switched off, a quiet setting or a deleted app will all swallow the message. So treat a push as a helpful nudge, never as proof that someone was told.

The fastest way to lose that permission is to send too much, and people rarely complain. They simply switch you off or delete the app, so you never find out why. Two messages a week that a customer actually wants will beat ten that annoy them. Linkysoft asks a client to list every message before we build the sending screen, and about half get cut in that meeting. Whatever survives should go out during working hours, in the customer's own time zone.

None of this gets bolted on at the end. When Linkysoft plans a mobile app project, the notification list is written before the first screen is drawn, because it decides what the system has to know about each customer.

Questions about Push Notifications

Do customers have to agree before I can send push notifications?
Yes. The phone or the browser asks once, and only a yes lets you send anything. There is no way around it, and there should not be.
Why do my notifications not arrive on iPhones?
A website can only push to an iPhone if the person added it to the home screen, which almost nobody does. For dependable delivery you need an installed app from the App Store.
How many push notifications a week are too many?
There is no fixed number, but past two or three a week without a real reason people start switching you off. Send when something changed that the customer already cares about.
Are push notifications the same as SMS?
No. A push costs nothing to send but only reaches people who installed your app or allowed your site. An SMS costs money for every message and reaches any phone number.
Can a customer turn push notifications off later?
Yes, in the phone settings at any moment, and nobody tells you it happened. A good app lets people keep the reminders they want and switch off the rest, which saves the permission.

Still not sure how this applies to your project?

Tell us what you are building and we will answer in plain language.