You don't need to. Unlike early versions of Android and apps that still link to older versions, with iOS, you have never had a list of permissions you had to accept before launching the app. The app ask permission when you need a feature and you can deny it the permission. After it asks once (three times?), it will never ask for the permission again and you have to go to settings to enable the permission.

You have a point but are also mistaken. XPrivacy does way more granular access checks than Android or iOS provide. The downside is, it's not casual user-friendly.

With XPrivacy you're able (or used to be able - I'm not sure if it works on recent Android versions) control things like how apps can use WebViews (e.g. what URLs they are allowed to open there), or whenever app is allowed to read or write (all separately) clipboard data. Etc etc.

I’m looking at a list of permissions here:

https://github.com/M66B/XPrivacy/blob/master/README.md

Most of these permissions either require individual consent after you run the app (and can be revoked in settings) or aren’t allowed under any circumstances.

The exceptions I see are:

Clipboard

Internet access (you can block cellular internet access on iOS and 3rd party keyboards can be blocked from allowing any network access)

Prevent links from opening in a view - depending on which type of web view that an app uses, the native content blocking framework that third party ad blockers use for Safari also work in the WebView. For instance, the ad blocker I have installed works with Feedly - my RSS reader.

The only sensor I think that can be blocked is the GPS.

XPrivacy is not about blocking, it's about faking.

PrivacyGuard in LineageOS is about blocking.

How is “faking” it better than just not allowing it all? iOS Developers have had to handle being denied permissions gracefully since 2008.

some apps don't work if the permissions are blocked. With xprivacy you can tell them

My phone number is 000 000 000 and my email is [email protected]

and they work fine then

And iOS doesn’t need that bandaid. App developers have been developing with the expectation that their apps could be denied permissions they request since day one.

Except for stuff that iOS doesn't ask and even implement a permission for. Like UIDevice.identifierForVendor.

Yes, you have more privacy with xprivacy, but at the same time, for running it, you need root access and install xposed, so you get +10 points for privacy and -5000 for security

Do you have a root access on your Linux PC? Does it add -5000 for security?

I have and I don't give access to root to my software. Also on my linux computer I can patch the very same moment there is a vulnerability, on my phone I can only patch security fixes when the manufacturer wants and only usually for 1 or 2 years.

Also, have you really audited the code of xposed and xprivacy to see that there isn't any single security flaw that expose your whole phone?