I don't think you've thought this all the way through. Once a user grants me permission to send them push notifications because they want to know when their ride shows up, you can't really stop me from pushing them ads through the same channel.
> Once a user grants me permission to send them push notifications because they want to know when their ride shows up, you can't really stop me from pushing them ads through the same channel.
Wait, can't an improvement upon the OS be to make it more granular so that Uber is forced to establish separate permissions channels for rides (vital) vs. ads (not-so-vital), and that every time a notification of a certain type appears, the user is given the option to mute that channel entirely?
My underlying point, of course, is just because the operating system provides certain APIs, does not mean they are going to be used in good faith.
Perhaps they could team up with Facebook and create a rival app store of those who don’t want to pay the 30% tax. Of which they can all hemorrhage users together- it should be noted that FB is also having issues maintaining and growing DAU.
> Sounds like a success story, imagine the alternative scenario where there was no review process and Uber could get away with this entirely.
It'd say 60-40. The 40% downside is that Apple deigned to go through with actually pulling Uber from the store, even just for a few days. Do you think they'd do anything even remotely similar over the notifications permission leak you cited?
> How does having more granular alerts actually solve this issue?
More restrictive and more transparent handling of permissions. Maybe this mechanism was caused by Uber bundling some sort of library that led to permissions leak. Perhaps the OS could expose that permission being triggered.