Earlier quoted context omitted.
Uber's Apps are so shit when it comes to that. I can rarely recall a time when I opened the app and closed it without finding anything useful and it didn't send me a notification within minutes.
I have the Uber Eats app installed and I don't receive unwanted notifications. I think I only enabled the channel for notifications on a current order, and I don't get anything else. Maybe they are more careful because I'm in the EU?
Push notifications – What to push, what not to push, and how often
71–80 of 159 posts
Re: Push notifications – What to push, what not to push, and how often
#72Earlier quoted context omitted.
yeah, I was like "you check the user's notification settings, right? right?"
The problem starts with low opt-in rates. The assumption becomes the low response was due to the user not understanding how to opt-in.
Re: Push notifications – What to push, what not to push, and how often
#73Earlier quoted context omitted.
No. Most customers will tolerate quote a lot of this form of advertising just like other forms. Enough to make it profitable to spend significant effort on it.
Whether customers will tolerate it has no bearing on whether it is acceptable to bake an antifeature into an application.
Re: Push notifications – What to push, what not to push, and how often
#74Two years ago I learned from some Twitter post a new habit: every time you install an app on your phone, you must do one more step: block its notifications. You don't need any notifications from apps as long as this is not an instant messaging app. (You can make additional exception for your banking app, but that's it for 90% of users) My phone is now so silent.
Re: Push notifications – What to push, what not to push, and how often
#75> But with pushes, we have to guess what the customer might be interested in given triggers such as events, promotional offers No, you don't have to guess. You can correctly know that the answer is "no". If you're going to blatantly send unwanted marketing to the user, at least be honest with yourself and your audience about it.
There’s literally no way we could break that down! How can we guess what the user wants when they REFUSE to tell us! I guess we better just leave it so they can opt out if they successfully navigate all 6 toggles, but if they do that we better just flag their account for suspicious activity because I don’t know why anybody would ever opt out. Seems suspicious to me.
Re: Push notifications – What to push, what not to push, and how often
#76While we can debate the merits/demerits of push - for practical commerce, a large part of the world still switches on push, and relevant push will deliver more concrete and better ROI.
Re: Push notifications – What to push, what not to push, and how often
#77Banking 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
#78Nothing. Everything. Never. /article In all seriousness, I recommend the app FilterBox, it allows you to set fine grained rules for notifications for each app
Re: Push notifications – What to push, what not to push, and how often
#79If 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.
Uber's Apps are so shit when it comes to that. I can rarely recall a time when I opened the app and closed it without finding anything useful and it didn't send me a notification within minutes.
Re: Push notifications – What to push, what not to push, and how often
#80I'd much rather the OS have a "report spam" button on notifications, and if more than 5% of app users report spam then the whole app gets all notifications blocked by default. Both Apple and Google have strong controls on the apps identity, so it won't be like email spam where the sender can just send from a new email address to get around the filter.
Seems like that would be a cheap way to destroy a competitor. Pay a bunch of people on some sketchy freelancer site to install the app, do whatever easily trigger notications.. and then report every single one. Sort of a spin in the concept that it’s much easier to create bullshit than debunk it.