The poster's point still stands, though. The user should decide whether to allow that permission on a case-by-case basis.
Sadly, that's a problem with Android, not Paypal.
Sadly, that's a problem with Android, not Paypal.
In fact, you're right. The main point is invalid, the author only saves face toward the final paragraphs, when mentioning iOS.
Perhaps developers should be able to explain permissions in the application's manifest file (where permissions are defined).
Or, maybe there should be a method by which permissions are permanently granted (as it is today), and a method by which permissions are granted on a case by case basis, asking the user's permission. With this model, installing the app would only notify the permanent grants. I'm probably forgetting something here, but this seems like an ok compromise between all or nothing and not harassing the user for the general (non-malicious) case.
That doesn't really solve the problem, though. The author of the post explains why, a description isn't needed. Of the Android apps I've installed that ask for more than I care to give, I can come up with reasonable explanations as to why they might need those permissions. But I just don't want to give them regardless of need, so I don't install the app.