Push notifications – What to push, what not to push, and how often
1–10 of 159 posts
Re: Push notifications – What to push, what not to push, and how often
#2If you send me a push and I can’t explain why I’m seeing it (for example, if it’s not time-sensitive or I haven’t done anything to indicate I want it) then I consider it spam. This is doubly so if you’re using it to send me an advertisement. That’s the easiest way to ensure your app is going in the trash.
Re: Push notifications – What to push, what not to push, and how often
#3> Thus, as we go from search to recommendations to pushes, it becomes harder to understand the customer’s intent
> Push notifications can be considered a form of recommender system
Recommender systems can also be viewed as a marketing optimization problem, which I guess would be the step beyond push notifications; recommending to future rather than current users. Interestingly, it has been shown that ‘expert consumers’ prefer user-based recommender systems https://www.sciencedirect.com/science/article/abs/pii/S09696....
Re: Push notifications – What to push, what not to push, and how often
#4If you send me a push and I can’t explain why I’m seeing it (for example, if it’s not time-sensitive or I haven’t done anything to indicate I want it) then I consider it spam. This is doubly so if you’re using it to send me an advertisement. That’s the easiest way to ensure your app is going in the trash.
I think this was covered:
> Another challenge is that irrelevant or unwelcomed pushes risk having the user disable notifications, uninstall apps, or start ignoring them due to low usefulness
> most recommendation engines take a myopic view, over-optimizing on immediate user responses at the cost of long-term satisfaction.
Re: Push notifications – What to push, what not to push, and how often
#5One detail not covered as much in this article is that many options are now available to users and apps to control the push notifications they send and receive.
For example, on iOS, when prompted for notification permission, users are now asked to choose if they want the notifications sent to a summary view. iOS will also invite users to disable notifications from apps they haven't interacted with recently.
Here are a few of the options available for each operating system. Many of these were introduced within the last 1 to 3 years.
iOS & Android:
* Apps can choose to send notifications without sound/vibration. These are less disruptive and less likely to result in an uninstall or disabling of push.
* Apps can customize which sound is sent with the notification, if any. On Android, the vibration pattern can also be customized.
* Apps can choose to replace an old notification with a new one. This helps prevent multiple updates from crowding a user's notification center (e.g. Order received, Order Arriving, Order Delivered)
* Apps can send notifications at different priority levels. On iOS, apps can even send notifications that break through a user's focus mode settings (e.g. for emergency alerts), but this requires special permission.
* Apps can group multiple notifications for easier readability (e.g. chat messages from different contacts)
* Apps can set a visual badge on their application icon, indicating the presence of new content, with or without also sending a push notification.
* Apps can choose between sending a push notification or starting a Live Activity. Live Activities have more visual customization and can show real-time updates such as sports scores or the status of a food delivery order. Starting with iOS 17.2, released in Dec 2023, Live Activities can be started remotely, just like push notifications. Prior to 17.2, users had to open the app to start them.
* Apps can implement Notification Channels, a way to categorize different types of notifications so that users can enable some but not others.Re: Push notifications – What to push, what not to push, and how often
#6I default block notifs (no, I refuse to call them properly, they are not worthy of that respect) on any and all newly installed applications. I might unblock later if it's useful or worth my time, but don't count on it.
Re: Push notifications – What to push, what not to push, and how often
#7Banking apps are the worst. They make us switch on notifications, else we can't get any confirmation notices for us to confirm transactions, then they proceed to spam me with credit card offers and other rubbish I'm not interested in receiving.
Re: Push notifications – What to push, what not to push, and how often
#8If you send me a push and I can’t explain why I’m seeing it (for example, if it’s not time-sensitive or I haven’t done anything to indicate I want it) then I consider it spam. This is doubly so if you’re using it to send me an advertisement. That’s the easiest way to ensure your app is going in the trash.
I think this was covered: > Another challenge is that irrelevant or unwelcomed pushes risk having the user disable notifications, uninstall apps, or start ignoring them due to low usefulness > most recommendation engines take a myopic view, over-optimizing on immediate user responses at the cost of long-term satisfaction.
It’s “covered” in that they write this and then immediately dive into an example where I buy a phone and start receiving push notification advertisements for buying cases. Do you think an app is going to ask me if I express interest in “related offers” or just start sending them unsolicited?
Re: Push notifications – What to push, what not to push, and how often
#9Banking apps are the worst. They make us switch on notifications, else we can't get any confirmation notices for us to confirm transactions, then they proceed to spam me with credit card offers and other rubbish I'm not interested in receiving.
This is especially annoying when they don't use different notification channels so I can't turn off individual types of notifications.
Re: Push notifications – What to push, what not to push, and how often
#10[deleted]