If my phone interrupts me, it should either mean someone genuinely needs my attention right now or it should not be disrupting me at all. That's my notification set up.
Apps allowed to receive push notifications
Phone,
Messages,
Whatsapp,
Apple Health,
[brand] bank.
That concludes the list.
There is no reason any other app needs to be able to instantly ping me. Most apps are not notifying you because something matters; they are notifying you because they want your attention.
I do not need notifications about streaks, sales, recommendations, delivery updates etc. All that can wait until I choose to open the app. It is not urgent enough to justify interrupting me.
The biggest problem are apps that do both. For example, I want Uber to notify me when my driver has arrived, but I don't want it to notify me when they have a special 10% discount on my next 5 rides. It's not straightforward to block one but not the other.
The user legitimately considers the application as hostile - hence sandboxing... Notification spam filtering is now the obvious need at the sandbox's edge. Of course, Google will not cooperate with anything likely to reduce sacro-sanct engagement !
And let's not forget focus modes... I have them that narrow greatly my default set of notifications, so I have a 3 tiers of notifications.
It's like the complaint I used to hear all the time: "Slack ruins work for me! OMG I can't work with constant interruptions!!" That is bewildering, because if that's how you feel, you haven't tuned your setup. Slack never interrupts me, yet I am response enough to slack messages. No one has ever complained about my response time. And I'm probably the most-messaged person on our Slack.
For Slack, I find just changing the default notification sound to a simple and subtle ding works well.
When I’m focused, I don’t hear it because it’s too subtle. But when I’m not concentrating on anything, it’s more noticeable and I don’t mind the distraction.
This might not work for everyone (“YMMV” and all), but I’ve personally found it a very effective yet simple solution.
Agreed. I have a doc appointment app, where I like the notifications to be on for reminders etc.
Lately they started sending marketing messages through that channel. Now I’m sure it’s possible to turn off the marketing messages. But I bet most people don’t know and won’t change that. It’s super annoying.
That's not entirely fair to the author as the article also states that the consumer being in control is a must:
> Every step subtracts a degree of sender control. Some of it passes to the user, and that is a good thing: a person deciding what is allowed to interrupt them is the channel working as it should. The rest passes to the platform, and that is the part that should concern a sender, because the platform's judgment is opaque, unappealable, and increasingly made by a model rather than by a setting the user chose.
A platform has essentially two "clients" - the user and the developer. Without both, it wouldn't exist. And it is in the interest of both that the platform should have very limited arbitrary authority over them. Nobody can deny today that the platform owners today have too much power over their users and their developers, which makes it easy for them to commercially exploit them while undermining their rights. We need regulations and standards (for interoperability, which is one of the arguments being made) to counter this.
Been an app developer since 2009, worked on Android for 6 years at Google. Push notifications suck, users hate them.
Simultaneously, I cannot match the pull quote, an argument summary, to their argumentation. IIUC if the reword patent / Apple’s summarizing disappear there’s 0 reason to say it wasn’t control passing purely to the consumer.
So I’m left a bit empty as the high-minded purpose has little backing, and thus comes across as bloviating.
is it unironically incomprehensible to you that the owner of the device should in the one who gets to decide what is and isn't spam? it's not email where you can get bombarded with shit from any random server - you can mute or uninstall an app.
I can’t think of a single app I want a “Discover” tab on anymore. The moment you include one is the moment there is someone trying to game it. I definitely don’t want push notifications trying to show me something new. I’m hardly lacking in distractions
(Yes I am sure somebody can give me an example of a good use of Discover but you get my point)
> For most of the channel's history they did very little of it visibly. The architecture was permissive of intervention; they simply chose not to intervene much. That restraint is what ended.
I guess it wasn't always visible, but they were intervening in some for or another since the beginning. At WhatsApp, push delay/suppression/coalescing was something we were always monitoring, and IIRC, it was part of the system since at least when I joined in 2011. If you don't work within the system, your users' messages don't get delivered timely.
Huh that’s interesting, do you have any further context on that? I’ve not worked on a product with anywhere near that scale before so monitoring has always been whatever I can get from commercial push platforms
I mean... record the time we first send a push message, when a client connects have it tell you if it's because it got a push or user interactive start, check the time between push and connection, add that to your choice of time series graphing tool. Graph by platform, and you can see when the platforms are delaying pushes.
Some of the delay will be ordinary things like their push service fell over or is unreliable (you also get some feedback when they don't accept push messages), or their push connection runs into silent NAT timeouts on some networks. But some of it will be things like you ran into an undocumented push quota, so Blackberry users don't get timely pushes at peak, etc. On client platforms where you have reliable background execution with network connectivity, you can potentially signal connecting clients if platform push isn't working well and have them switch to persistent connections until the push service comes back. But that was never an option for iOS; it hasn't been a reasonable option for Android since at least Android 6 when Doze was introduced... and app killers before then made it hard before then; and all the other platforms are dead. Now, push really just has to work.
AFAIK, Apple has always been willing to deprioritize pushes when you send "too many", especially when there's no user interaction; or when they added silent (voip) pushes to wake up the app, they only let you have a few silent pushes if you don't post a user visible push.
For ordinary async messaging, push latency doesn't become a big deal until it hits double digit seconds. For voice/video calls, you really want pushes to be as near to real time as possible, or the caller is gone before the callee phone rings.
I see the point. But honestly I am more concerned about having to constantly fight to turn off all permission allowances every time I install an app.
And the moment I have some faith and trust an app that I deem important, I get promotional junk as a "notification".
I would really like to have notifications allowed on certain apps like parking, or health etc., but all they seem to do is abuse the trust they are given, meaning I turn them off.
So where I agree with this author is certainly that more power belongs at the user.
> None of this bites evenly. The editing falls hardest on broadcast and promotional push; the notifications people actually want tend to pass through untouched or amplified.
I wish apple/google would implement better notification control - like the ability to turn off all marketing notifications, and a much better digest format
Notification Channels is the official way to do this on Android, but it's up to the app developer to categorize them properly. They have no incentive to allow you to turn off ads.
That would be nice. I wouldn’t be surprised, as on-phone models get more capable, if we don’t see them start to build an “inbox” like we see with email where you can then start seeing much more heavy processing happening.
I think that's what the Notification Organizer on Android (maybe Pixel exclusive, not sure) does. It's sorting notifications into broad categories using AI and groups them in the notification shade.
> Over fifteen years the channel has been rebuilt around one assumption: the receiver's attention is a scarce resource the platform is obliged to defend. … As a sender you are on the wrong side of that assumption, whichever way the control moved.
Fascinating how the author openly frames the situation as the sender and receiver’s interests being opposed.
Massively overlong article that really could have done with an editor. Although obviously editors cost money, and I'm reading it for free, so I can scarcely complain. Nevertheless, some concision would have been appreciated.
I'm very unclear to me what the thesis of the article actually is. Yes, push notifications run through the vendor's servers. Yes, Apple fucked up hard by modifying the text within them - and I contend that such modification is impossible to perform automatically without unreliability becoming the norm.
The author also appears to believe that "broadcast copy" - otherwise known as Spam by those who like to write slightly more honestly - is a legitimate use of push notifications. It is manifestly not, and any app that tries will at the very least be immediately silenced. I wish I could find the tweet that put this sentiment more entertainingly than I ever could.
If App developers continue to abuse the push notification system in this way, Apple and Google will be forced to take steps to solve what becomes an end-user's problem. Yet another tragedy of the commons.
If my phone interrupts me, it should either mean someone genuinely needs my attention right now or it should not be disrupting me at all. That's my notification set up.
Apps allowed to receive push notifications
Phone, Messages, Whatsapp, Apple Health, [brand] bank.
That concludes the list.
There is no reason any other app needs to be able to instantly ping me. Most apps are not notifying you because something matters; they are notifying you because they want your attention.
I do not need notifications about streaks, sales, recommendations, delivery updates etc. All that can wait until I choose to open the app. It is not urgent enough to justify interrupting me.
The biggest problem are apps that do both. For example, I want Uber to notify me when my driver has arrived, but I don't want it to notify me when they have a special 10% discount on my next 5 rides. It's not straightforward to block one but not the other.
The user legitimately considers the application as hostile - hence sandboxing... Notification spam filtering is now the obvious need at the sandbox's edge. Of course, Google will not cooperate with anything likely to reduce sacro-sanct engagement !
Agreed.
And let's not forget focus modes... I have them that narrow greatly my default set of notifications, so I have a 3 tiers of notifications.
It's like the complaint I used to hear all the time: "Slack ruins work for me! OMG I can't work with constant interruptions!!" That is bewildering, because if that's how you feel, you haven't tuned your setup. Slack never interrupts me, yet I am response enough to slack messages. No one has ever complained about my response time. And I'm probably the most-messaged person on our Slack.
For Slack, I find just changing the default notification sound to a simple and subtle ding works well.
When I’m focused, I don’t hear it because it’s too subtle. But when I’m not concentrating on anything, it’s more noticeable and I don’t mind the distraction.
This might not work for everyone (“YMMV” and all), but I’ve personally found it a very effective yet simple solution.
> if that's how you feel, you haven't tuned your setup
The withering cry of the software engineer "just tune your setup!" This is simply not a thing that people will do.
The defaults are so, so important. They are crucial. The vast majority of people rely on the defaults to be sane. The defaults should be sane.
If you are very present on slack, ofcourse you dont feel that you are interruped.
To your list, I would add a calendar and reminders app.
I feel like this article reads like the author is upset that Apple + Google prevent / control certain types of notifications (read: spam)
> Cross-sell, upsell, education and discovery can work on push
Push notifications should only be for transactional notifications. I don't want another inbox for junk.
Agreed. I have a doc appointment app, where I like the notifications to be on for reminders etc.
Lately they started sending marketing messages through that channel. Now I’m sure it’s possible to turn off the marketing messages. But I bet most people don’t know and won’t change that. It’s super annoying.
Same for things like Uber.
I do want to know when a car is arriving.
I don't want messages asking if I'm hungry.
And soon, those appointment reminders might quietly be dismissed by your phone without you being any the wiser.
That's not entirely fair to the author as the article also states that the consumer being in control is a must:
> Every step subtracts a degree of sender control. Some of it passes to the user, and that is a good thing: a person deciding what is allowed to interrupt them is the channel working as it should. The rest passes to the platform, and that is the part that should concern a sender, because the platform's judgment is opaque, unappealable, and increasingly made by a model rather than by a setting the user chose.
A platform has essentially two "clients" - the user and the developer. Without both, it wouldn't exist. And it is in the interest of both that the platform should have very limited arbitrary authority over them. Nobody can deny today that the platform owners today have too much power over their users and their developers, which makes it easy for them to commercially exploit them while undermining their rights. We need regulations and standards (for interoperability, which is one of the arguments being made) to counter this.
Been an app developer since 2009, worked on Android for 6 years at Google. Push notifications suck, users hate them.
Simultaneously, I cannot match the pull quote, an argument summary, to their argumentation. IIUC if the reword patent / Apple’s summarizing disappear there’s 0 reason to say it wasn’t control passing purely to the consumer.
So I’m left a bit empty as the high-minded purpose has little backing, and thus comes across as bloviating.
Not upset, but increasingly concerned that all channels are being intermediated by big tech.
> (read: spam)
is it unironically incomprehensible to you that the owner of the device should in the one who gets to decide what is and isn't spam? it's not email where you can get bombarded with shit from any random server - you can mute or uninstall an app.
It should but apps don't let us decide.
An intermediate seems to be trying to fix it.
Is it ideal? No. But it's the spammers who are to blame.
Yeah these channels used to be respected in that way.
And then app developers discovered that hooks like "look what you missed" work on users and so now we all have to get them in the same category.
>discovery
I can’t think of a single app I want a “Discover” tab on anymore. The moment you include one is the moment there is someone trying to game it. I definitely don’t want push notifications trying to show me something new. I’m hardly lacking in distractions
(Yes I am sure somebody can give me an example of a good use of Discover but you get my point)
> For most of the channel's history they did very little of it visibly. The architecture was permissive of intervention; they simply chose not to intervene much. That restraint is what ended.
I guess it wasn't always visible, but they were intervening in some for or another since the beginning. At WhatsApp, push delay/suppression/coalescing was something we were always monitoring, and IIRC, it was part of the system since at least when I joined in 2011. If you don't work within the system, your users' messages don't get delivered timely.
Huh that’s interesting, do you have any further context on that? I’ve not worked on a product with anywhere near that scale before so monitoring has always been whatever I can get from commercial push platforms
I mean... record the time we first send a push message, when a client connects have it tell you if it's because it got a push or user interactive start, check the time between push and connection, add that to your choice of time series graphing tool. Graph by platform, and you can see when the platforms are delaying pushes.
Some of the delay will be ordinary things like their push service fell over or is unreliable (you also get some feedback when they don't accept push messages), or their push connection runs into silent NAT timeouts on some networks. But some of it will be things like you ran into an undocumented push quota, so Blackberry users don't get timely pushes at peak, etc. On client platforms where you have reliable background execution with network connectivity, you can potentially signal connecting clients if platform push isn't working well and have them switch to persistent connections until the push service comes back. But that was never an option for iOS; it hasn't been a reasonable option for Android since at least Android 6 when Doze was introduced... and app killers before then made it hard before then; and all the other platforms are dead. Now, push really just has to work.
AFAIK, Apple has always been willing to deprioritize pushes when you send "too many", especially when there's no user interaction; or when they added silent (voip) pushes to wake up the app, they only let you have a few silent pushes if you don't post a user visible push.
For ordinary async messaging, push latency doesn't become a big deal until it hits double digit seconds. For voice/video calls, you really want pushes to be as near to real time as possible, or the caller is gone before the callee phone rings.
I see the point. But honestly I am more concerned about having to constantly fight to turn off all permission allowances every time I install an app.
And the moment I have some faith and trust an app that I deem important, I get promotional junk as a "notification".
I would really like to have notifications allowed on certain apps like parking, or health etc., but all they seem to do is abuse the trust they are given, meaning I turn them off.
So where I agree with this author is certainly that more power belongs at the user.
Apart from this, what is most needed in both platforms is an application firewall - not every app needs to be allowed to connect to the internet.
> None of this bites evenly. The editing falls hardest on broadcast and promotional push; the notifications people actually want tend to pass through untouched or amplified.
Sounds fine with me?
I wish apple/google would implement better notification control - like the ability to turn off all marketing notifications, and a much better digest format
Notification Channels is the official way to do this on Android, but it's up to the app developer to categorize them properly. They have no incentive to allow you to turn off ads.
That would be nice. I wouldn’t be surprised, as on-phone models get more capable, if we don’t see them start to build an “inbox” like we see with email where you can then start seeing much more heavy processing happening.
I think that's what the Notification Organizer on Android (maybe Pixel exclusive, not sure) does. It's sorting notifications into broad categories using AI and groups them in the notification shade.
Makes sense, Google definitely have a lot more experience in that space with gmail than Apple do.
> Over fifteen years the channel has been rebuilt around one assumption: the receiver's attention is a scarce resource the platform is obliged to defend. … As a sender you are on the wrong side of that assumption, whichever way the control moved.
Fascinating how the author openly frames the situation as the sender and receiver’s interests being opposed.
A fairly uncharitable read, I’d argue it states that the platform is acting on the platform’s interest, not the user’s.
Massively overlong article that really could have done with an editor. Although obviously editors cost money, and I'm reading it for free, so I can scarcely complain. Nevertheless, some concision would have been appreciated.
I'm very unclear to me what the thesis of the article actually is. Yes, push notifications run through the vendor's servers. Yes, Apple fucked up hard by modifying the text within them - and I contend that such modification is impossible to perform automatically without unreliability becoming the norm.
The author also appears to believe that "broadcast copy" - otherwise known as Spam by those who like to write slightly more honestly - is a legitimate use of push notifications. It is manifestly not, and any app that tries will at the very least be immediately silenced. I wish I could find the tweet that put this sentiment more entertainingly than I ever could.
If App developers continue to abuse the push notification system in this way, Apple and Google will be forced to take steps to solve what becomes an end-user's problem. Yet another tragedy of the commons.
> Google followed in 2010 with Cloud to Device Messaging, then Google Cloud Messaging in 2012, then Firebase Cloud Messaging in 2016
Classic
Push notifications are for the user, not the marketer.
From the author's blog: "I do Revenue Operation, helping Marketing, Sales and Customer Success teams with data, process and technology."
You think there might be some sort of interaction between both facets there?
How is bad summarisation good for a user, for example?
I'm surprised that the article is this long with zero mention of Senator Wyden's concerns vis-a-vis Google and Apple's Push Notification system: https://www.wyden.senate.gov/imo/media/doc/wyden_smartphone_...
I’m in the UK so I don’t catch all us news, good spot though