> When you install FB or any other app you get a nice list of things the App is allowed to do, if you do not want the app to do those things you should not install the app.

This is actually a fairly recent change to Android. It did not used to provide you with these choices. It demonstrates that user privacy is a bit of an afterthought with Android.

For Apple, these kinds of user choices have been there since the start.

>>This is actually a fairly recent change to Android

if by "recent" you mean "almost since the beginning" then sure.

The app permissions system has gotten better over time, more fine grained, ability to deny permissions while still install the app, and other features, but the basic list of "if you install this app it gets X access" has been there for a long long time, v2 or v3 if I remember correctly

The ability of accepting/rejecting specific permissions is from Android 6.

Yes but my comment was "Displays a list of permissions" not allow you to pick which permissions

I do not believe the first version if iOS has the ability to reject specific permissions either.

The first version of iOS didn't have apps, so this wasn't an issue…

I've been using Android since 2.x and I sell to remember it has always been like this. The recent change iirc is being able to decline a certain privilege and still use the app.

No, only Android 6 and later has provided proper user permissions [0] :

> You declare that your app needs a permission by listing the permission in the app manifest and then requesting that the user approve each permission at runtime (on Android 6.0 and higher).

> Beginning with Android 6.0 (API level 23), users can revoke permissions from any app at any time

[0] https://developer.android.com/training/permissions/requestin...

It got better in Android 6.0 but it was as described long before that.

Yeah, they'd show you a list of a dozen things that the app was going to use and you basically just tapped the "accept" button because you wanted the app to have access to your photos except now it has access to your contacts, location history, notification center, and firstborn child. Android Marshmallow brought improvements in this area, though.

Yes an a responsible person that downloaded a photo app that requested access to "your contacts, location history, notification center, and firstborn child" would choose not to install it.

If you continue to install those apps you only have yourself to blame IMO

But on Android pretty much any app does this. Just look at what Google Photos needs: https://play.google.com/store/apps/details?id=com.google.and...

Using a Core Android App developed by Google, that used to be a part of ASOP, and it required to be installed on all Play Store Eligible Android Devices is not a good example of "Pretty much any app does this"

I have all kinds of apps that do not do this, only asking for permissions they need

Which is exactly what the comment was talking about.