5 ms·
As an Android developer, I don't want to have to ask for as many permissions as I do. I have 1 button buried on 1 screen that allows you to call customer suppor
by krschultz 12y ago
As an Android developer, I don't want to have to ask for as many permissions as I do. I have 1 button buried on 1 screen that allows you to call customer support. 99.9% of users never click the button. However, I have to make every single customer accept the CALL_PHONE permission.
There are a bunch of permissions required for basics like autocompleting the users email for login, or checking the network state so you can adjust the app behavior based on connectivity.
Not to mention the incentives are all wrong in the Play store. Changing permissions murders your update rate, so you want to do it as little as possible. So when you are forced to add a permission, you grab a bunch of extra ones you 'plan' to use later to avoid having to get over that hump again. It's really awful.
- driverdan 12y agoWhy? All we have is a tel: link that opens the phone number in the dialer. They can choose to initiate the call or not, no permissions needed.
- pja 12y agoA guess: The call might show up in the phone logs if it's made through the standard Android Phone app. If the call is made directly from the Uber App, then perhaps this means that Uber can hide the phone number from the user. I can think of a number of reasons why they'd want to do that if they could.