No question that Google has just been trying to ape Apple lately, but for mobile specifically there are actually lots of features that android and its ecosystem had for years before Apple finally added (copied) it for iOS.

With permissions, before Google started to copy Apple's system, there was no such thing as an Android user being able to deny an app permission to do something. Either you gave the app permission to do everything it wanted, or you couldn't install the app at all.

Isn't the next version of Android the first time users will be allowed to deny an app permission to send notifications? That's been in iOS from the start and has always provided a way to silence apps that spam notifications.

Android has had the ability to turn off notifications since Android 4.1 (July of 2012) and I'm pretty sure the ability to turn off notifications on iOS was added in iOS 5 (October 2011)

iOS only added permissions at all in iOS 6, before that apps had access to photos, calendars, contacts and reminders automatically.

>One of the most notable changes in Android 13 is the new runtime permission model for notifications. In previous Android versions, apps could post notifications by default without requesting any permission.

https://www.xda-developers.com/android-13-beta-3-review-noti...

Yes, notification permission was previously granted by default, because the ability to block an app from sending notifications predates the concept of affirmative app "permissions".

Android has recently been refining their notifications model, increasing the granularity of the notifications by splitting them into "types" and user-assigned "priority" levels. It seems default-off is the newest step in that, apparently.

Android has had the ability to disable notifications for at least the last few years.

>Android 13 (API level 33) introduces a new runtime permission for sending non-exempt notifications from an app: POST_NOTIFICATIONS. This change helps users focus on the notifications that are most important to them.

https://developer.android.com/about/versions/13/changes/noti...

They did? I'm not in the Apple ecosystem, but I thought privacy and control over your apps was Apple's thing?

Has Apple shown a list of raw app entitlements? They always prefer "simplicity" to user control

Entitlements aren't permissions. There are a lot of operating system services which are privacy-relevant, but which don't have associated entitlements (e.g. location services or contacts access), and a lot of entitlements that aren't related to permissions (like ones that let an application request an increased memory limit, or allow it to store data in iCloud).

Here's a full list of entitlements from Apple. You'll find that a lot of them wouldn't make sense to display on a store page:

https://developer.apple.com/documentation/bundleresources/en...

Never. But they have “privacy nutrition labels” that show what data is tracked either anonymously or linked to you. It’s quite helpful, and likely easier to read than a raw list of permissions.

https://www.businessinsider.com/what-are-apple-privacy-nutri...

When I saw this post I assumed Google was rolling back their privacy nutrition label like things they added. I didn’t realize it was about the granular list.

How is it working for Apple?