Add it and that’s it Many Apps with the dominion are free to send me notifications, until I’m angry enough to tell them to refuse. I can (and should) uninstall some of these, but others I need to keep on my phone. I just don’t want them spamming me telling me the developer has updated their weird desktop photo management app that I’ll never use.
To make matters worse, creating notification categories is only up to the developers. But developers don’t have to play well. Amazon, for example, only uses three categories in Android (“notifications,” account authentication, and Alexa) but is improving them in the app itself. If you try to silence or disable push notification advertising, you can accidentally disable shipping notifications. (And at least in the past, Amazon has Make charitable donations conditional on receiving personalized ad notifications.)
Even when developers – including Google – play by the rules of the system, it’s easy to create new notification categories to get around the ones a user has silenced. The main Google Android app has 30 different categories of notifications, currently including things like Tips and Tricks, Recommendations, and Miscellaneous. Good luck figuring out what they all mean. Oh, and They are always changing.
Force apps to ask for permission Before Sending notifications won’t fix all this. People may still give Amazon permission to send notifications, only to be stuck with some ads coming in because, well, they still want delivery updates. However, being able to cut up some trash before it arrives is better than chasing after the fact.
The problem is with the way Android updates work, even this simple and necessary change would take years to have a major impact. Android updates take some time to roll out to most users. As of May 2022, only 28.3 percent of Android devices It was in version 11 or later. Android 11 debuted in 2020. In other words, it may be years before your phone supports this feature.
Even if you are one of the lucky few who owns a phone (maybe Samsung or Google Pixel) that will support soon, developers will not be required to support it yet. probably will be From mid to late 2023 Before apps will be asked to target Android 13, and in doing so, you’ll have to ask for permission before notifications can be sent. This may be urgent for some applications, but others may hold for as long as possible.
Given how long it will take for the Android ecosystem to keep up with this change, how important this basic permission is, and especially considering how much attention Google has paid to its notification system… it’s shocking that this is happening so late.
When I first bought the T-Mobile G1, both my and The First Android phone – Notifications were one of the things I was most excited about. It was a handy little to-do list of all the things I needed to answer sitting at the top of my phone, and over time I was even able to take care of some of these tasks without leaving the shade.
Today, notifications on Android have become a little nightmare. I had to uninstall apps that I would otherwise use only because it became too tiring to keep track of all the unwanted notifications. I no longer trust that if my phone rings, it must be something important. And the time I need to spend just making sure the apps behave the way they should grow exponentially. I’m glad Google finally asked for permission instead of forgiveness. I wish he had done that a lot sooner.