<p>Published on <a href="https://blog.prototypr.io/3-best-practices-for-in-app-permissions-dce7d36544a4?source=rss----eb297ea1161a---4">| Prototyping: From UX to Front End &mdash; Medium</a> inapptics <img alt="" src="https://cdn-images-1.medium.com/max/800/1*k5ZDuLATLJ3YhHtD-02kqA.jpeg"></p>
<p>It’s a smart move from Google and Apple to let users decide which permissions they want to allow or revoke. This in mind, it’s a good idea that you as an app maker think of building attractive in-app permissions. Permission requests are there to protect sensitive information that is on the device. Permission requests should be used to only access information necessary for the functioning of the app.</p>
<p>How apps ask for permissions differs from app to app. But the challenge for iOS app makers is that iOS gives you the ability to ask for a permission only once. So you have to get creative. Otherwise, the user should go find out how to turn the permission back on in OS settings. So, let’s now look at a few scenarios of in-app permission requests and see which of them are bright and which ones are total disasters.</p>
<h3>1. Asking right away</h3>
<p>Some apps ask for in-app permissions right away as soon as the <a href="http://blog.inapptics.com/enhanced-user-onboarding-tactics/">onboarding</a> is completed. This is, of course, the easiest thing to do. But at the same time, it’s the hardest to recover from. Because if you waste the chance of asking again, then you might not get it back anymore. For some apps, it’s strategically important to ask for certain types of permissions right at the beginning. For example, Tinder asks its users whether it can access their location or not since its recommendations are based on the user’s location.</p>
<p><img alt="" src="https://cdn-images-1.medium.com/max/280/1*4fQ1F2i61HJRnusT_UmM0Q.png"><a href="https://medium.com/product-breakdown/5-ways-to-ask-users-for-ios-permissions-a8e199cc83ad">Image source</a></p>
<p>But we have got mixed feelings about this kind of in-app permission requests. While some people might be excited and might actually allow the app to access their location, others might simply turn down the annoying message without even reading it properly. So you might be risking it. And it’s just 50/50.</p>
<h3>2. Asking twice</h3>
<p>Yes, we have already said that you can only ask for an in-app permission once but that does not mean that you cannot play a little dirty game by first asking one preparatory question to the user. It’s like letting the user know that you might be asking them for a permission to access information. Polite, right? Take a look at the below example:</p>
<p><img alt="" src="https://cdn-images-1.medium.com/max/646/1*wC2u26QGSRcixZzxSNqOnw.png"><a href="https://www.braze.com/academy/Best_Practices/#push">Image source</a><img alt="" src="https://cdn-images-1.medium.com/max/649/1*mwlQNkRFsv5Q58kNvLiE-g.png"><a href="https://www.braze.com/academy/Best_Practices/#push">Image source</a></p>
<p>The first request is not the actual in-app permission request. It serves as a simulation. The second one is the real OS prompt. But the user sees it only after agreeing in the first message. Doing this can provide 2 benefits:</p>
<ol>
<li>If the user denies the first in-app permission request, the app can still show them the real OS prompt later on, after considering a better timing.</li>
<li>The first message can teach about the importance of giving in-app permissions and the user might be more eager to granting access at the second time.</li>
</ol>
<h3>3. Asking as soon as the user takes an action</h3>
<p>Another thing you can do is to wait until the user comes to the point where they have to take an action themselves. For example, they click to upload a photo and you ask for a permission to access their Gallery. This approach is as simple as pie! And the good thing here is that since the app is asking for a permission in a certain context, the user is less likely to deny it.</p>
<h3>Bonus tip</h3>
<p>Whenever you are asking for an in-app permission, make sure you provide enough context and you focus on the value proposition. In the end, you are asking for a permission to provide your users with something useful, so make sure you are describing your actions in an informative and understandable way. Look at the examples below:</p>
<p><img alt="" src="https://cdn-images-1.medium.com/max/560/1*t7EIw6uBiIEN838Jnx4r3Q.png"><a href="https://uxplanet.org/getting-to-yes-best-practices-for-ios-permissions-dialogs-9d62892142cc">Image source</a></p>
<h4>At the end</h4>
<p>Overall, avoid requesting unnecessary permissions. Don’t ask for sensitive data such as the phone’s IMEI number. Do not request to take a full control over the Wi-Fi or data connection. This is unethical!</p>
<p>Also, remember that every time you ask for a permission, you force the user to take action, to make a decision, to do something that they were not thinking of doing. Hence, make sure to minimize the number of times you ask for in-app permissions. You don’t want to distract your users and to eventually bore them, right? Think about it!</p>
<p>Curious to know what users do in your app? <a href="https://inapptics.com/?utm_source=Prototypr%20footercta&amp;utm_medium=footercta&amp;utm_campaign=Blog_footercta_prototypr"><strong>Try Inapptics for free</strong></a><strong> </strong>and visually see every actions users do in your app, e.g. where they tap, how they navigate, what they did that caused the crash you can’t reproduce and more.</p>
<p><strong><em>If you enjoyed this article, feel free to hit that clap button 👏 to help others find it.</em></strong></p>
<p>Follow Inapptics: <a href="https://medium.com/@inapptics">Medium</a> | <a href="https://twitter.com/inapptics">Twitter</a> | <a href="https://www.facebook.com/inapptics/">Facebook</a></p>
<p><em>Originally published at </em><a href="http://blog.inapptics.com/in-app-permissions-best-practices/"><em>blog.inapptics.com</em></a><em> on April 19, 2018.</em></p>
<p><strong>Read Next:</strong></p>
<ul>
<li><a href="http://blog.inapptics.com/mobile-heatmap/">Mobile Heatmap: One of the Best Tools to Visualize User Behavior</a></li>
<li><a href="https://uxplanet.org/how-to-effectively-measure-ux-with-google-heart-framework-4a497631d224">How to Effectively Measure UX with Google HEART Framework</a></li>
<li><a href="https://blog.prototypr.io/best-practices-for-designing-mobile-app-error-states-c065d66086b6">Best Practices for Designing Mobile App Error States</a></li>
</ul>
<p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&#038;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%252F%253Fenpose&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=dce7d36544a4" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou"></p>
<hr>
<p><a href="https://blog.prototypr.io/3-best-practices-for-in-app-permissions-dce7d36544a4">3 Best Practices for In-App Permissions</a> was originally published in <a href="https://blog.prototypr.io">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>


3 Best Practices for In-App Permissions

Top Stories