After you install an app and open it for the first time, you automatically receive permission to send notifications. You can always block their notifications later, but that involves an extra step. According to the latest rumors, in Android 13, apps they will not automatically get notification permission: they have to ask.
Notifications will now work the same way as location, microphone, or camera access: an app that wants to send them will need to request the new permission at runtime. POST_NOTIFICATIONS. We now have a screenshot courtesy of Android Police of what this permission request will look like.
Authorization to notify
They start coming harder and harder Android 13 leaks. If Google follows the pattern of other years, the first Developer Preview of Android 13 could be in a few weeks. In the meantime, we get almost daily leaks of leaked preview builds.
One of the most drastic changes in Android 13 will be that notifications will be one more permission. Until now, it was possible to turn off notifications from any app, but they were technically not a permission. We have already seen that the new permission will appear in Android settings and in the info section of any app.
Therefore, starting with Android 13, apps will need to request permission to send notifications before they can do so. Now we know that the window that will appear gives us only two options Allow or deny. There are no intermediate options.
Until Google shows us the first Developer Preview of Android 13, we won’t know how it will affect apps or whether the restriction will apply to all apps in Android 13 or only those created pointing to the latest API.
A possible headache will come with the automatic revoking of permissions introduced in Android 11, as this could mean that you also lose notifications from those apps that should notify you from time to time (eg a calendar or a sporadic reminder).
Via | Android Police
