How should an Android permission that looks fishy for the app but without which it's impossible to obtain a certain needed behavior be handled?

Question

To be honest, I'm not 100% sure if the ways to achieve that behavior only are possible through that permission, or even if there's some workaround of that behavior, but I'm almost sure so I'm posting.

Going to the particular case, I'd need for my Android app to check what's the signal strength with which the device is connected to the telephony network, and it looks like that's impossible to do without having enabled the permission for accessing user's location.

Problem is that app doesn't look like it has anything to do with needing user's location, indeed, if it's only possible through that permission, I consider that a fail in Android design from user experience point of view, so my guess is that it could make some users suspicious about that, specially considering that from Android API 23 you need to explicitly confirm a dialog to allow the permission.

I guess I'd need some very good words not to make the user suspicious, or well, maybe I'm also overlooking the users that would feel suspicious about my app.

Which would be a good way to handle this in terms of user experience if on last instance that permission is needed to achieve that behavior?

Answer 1

As you mentioned, asking for unnecessary permissions hurts your credibility. You need a good reason to ask for what you want. A new user doesn’t know the first thing about how this app works, so they have no incentive to say yes. What you could do - if there truly are no workarounds - is use priming screens.

You didn't mention what your app does, but permission priming works in a way that you add context to the permission; you show what your user will before they're hit with the permission request. There's multiple ways to do this, but a simple rule is: Make sure it’s crystal clear for users what they’ll get in return for accepting the request.

These examples are iOS centered, but the same principle applies.

1. Benefit Explanation

Explaining a permission in context is another well-done example — it helps gauge user interest and improve comprehension of the permission. Try to explain to a user the benefits they’ll receive by giving the app access.

2. Priming During The Request

You can do this by providing a background image that explains the permission request. Foursquare primes users by providing a background image that explains why the app needs that particular permission.

3. Primer” Message Before Actual Permission Request

In most cases, it’s better to “prime” your users to accept requests before the actual permission request screen appears.

4. Ask In Context of Action

User-triggered dialog works even better that context-building screen, because users are expecting the request and more likely to allow a permission when they want to use the feature it enables. Wait until a feature is invoked to request permission. When the user taps a feature like the camera in Cluster app, that triggers the request for photo permissions.