--- title: "Don’t Rush to Request App Permissions: You Need a Strategy" locale: "en" language: "en-HK" published: "2016-06-16T13:05:33+08:00" updated: "2026-03-17T23:07:22.697Z" canonical: "https://accordhk.com/blog/dont-rush-to-request-app-permissions-you-need-a-strategy-285" --- # Don’t Rush to Request App Permissions: You Need a Strategy Early interactions shape users’ impressions of an app. A barrage of unexplained permission requests can drive them away; a clear strategy helps you ask at the right time and explain the value. ## In brief Request essential permissions at the start and ask for others in the relevant context. Explain the benefits, prepare users before system prompts, and show them how to restore essential permissions they have denied. Did you know that, on average, each [app]() loses 80% of its average daily active users within the first three days after installation? Most users download an [app](), open it once, and then uninstall it. This happens because, although users are willing to try installing many [apps](), they still have to decide which ones to uninstall during those first few days. Do users do this because your [app]() is poorly made? Not entirely, but users’ initial interactions with your [app]() do play a major role in shaping their overall impression of it. As things stand, when users open a new [app](), the first thing they often see is a series of pop-ups asking them to grant permissions. This approach has a significant impact on the user experience and often leads users to stop using the app. The right approach is for an [app]() to establish some dialogue with users before requesting permissions. I. Develop a strategy When requesting permissions, the worst thing an [app]() can do is bombard users with requests without any explanation. Asking too early or asking for too many permissions at once are common mistakes. Yet many [apps]() still do this: users launch the [app]() and immediately encounter requests they do not understand. For example, Google’s Inbox even requests permissions before users have signed in to the [app](), without providing any additional information or context. When you request a permission, you naturally want every user to accept. To achieve this, you should develop a strategy based on how clear and important the permissions you request are. Essential permissions should be requested at the start, while less important ones can be requested in context. II. When to ask users One of the most important factors determining whether users accept or reject your request is when you ask them. 1. Request only essential permissions at the start For many [apps](), failing to obtain access to data can change the entire user experience. For example, if an [app]() depends on SMS services, it cannot be used without that permission. Fortunately, most users expect a messaging app to request SMS access, so asking for this permission upfront makes good sense. If a feature needs several permissions to work properly, request only those permissions and avoid asking for any unrelated ones. 2. Request permissions in the context of use In most cases, making a new user endure a stack of permission requests at the outset can cost you a crucial opportunity to retain them. [Apps]() should request permissions in a relevant context during use and communicate the value of granting them. Once you have encouraged users to stay, they are more likely to accept your requests as they use the app. III. How to ask users [An app]() must make clear why each permission is necessary, whether through a feature name or an explanation. Remember, if you want users’ consent, you need to ask in the right way and at the right moment. 1. Explain the benefits When the reason for a permission request is unclear, explain what it involves. If your app has an introductory walkthrough, use it to explain what the app can do and why even unexpected permissions are necessary. Explaining a permission in the context of use is another effective approach: it engages ordinary users and helps them understand the permission better. Make a point of explaining the benefits users can receive after granting it. 2. Offer guidance while making the request Foursquare guides users’ choices by providing a background image that explains why the [app]() needs a particular permission. 3. A preliminary dialogue before the actual permission request You can trigger the default iOS permission request only once for each feature. One of the most frustrating situations for users is denying a permission at the system level and then finding it troublesome to grant access again for a particular [app](). In most cases, it is better to present a preliminary request before the actual iOS system permission screen. 4. Ask after a user action Request dialogs triggered when users activate a feature work better because they appear when users want to use that feature, making users more likely to grant the permission. IV. How to handle permissions users have denied Denying a permission may prevent a feature from producing the expected result, so explain the situation to users whenever a permission has been disabled. Essential permissions: If an [app]() cannot function properly because an essential permission has been disabled, explain why that permission must be granted and provide a link or path that lets users enable it again. V. Conclusion Although every app is undoubtedly different, you should carefully consider when users need to grant access to particular permissions or data on their phones, and make sure they expect to be asked. Improving the user experience is an ongoing process. Do not miss opportunities to prepare users to accept permission requests, and test different scenarios to see what works best for your app. http://www.hksilicon.com/articles/1110046 ## Frequently asked questions ### Which permissions should an app request at the start? Request only permissions essential to the app’s operation or the feature being used. If a feature requires several permissions, ask for those and avoid unrelated requests. ### When should an app request less essential permissions? Ask in the relevant context, when users are using or activating a feature that needs the permission. Explain the value of granting access at that moment. ### Why use a preliminary dialogue before an iOS permission request? The article states that the default iOS permission request can be triggered only once for each feature, and restoring access after denying it can be troublesome. A preliminary dialogue helps prepare users before the system request appears. ### What should an app do when a user denies an essential permission? Explain why the permission is needed for the app to function properly. Provide a link or path that lets the user enable it again.