The psychology behind the authorization

The optimal “permission handling”, as this type of access request is called, can decide whether users are gained or lost. This is where psychology meets user interface design. How do we ask for permissions? When do we ask? How much information do users need to make a decision? And how much information do we want to ask for? After all, the app should not become a data octopus. For Maria Timonen, UX Design Lead at Bitforge, these questions are part of everyday life. “Users are now very aware of this – even children. It’s an important topic,” she explains. When planning the UI, Maria considers three key points when dealing with permissions in order to make it as pleasant as possible for users to click on “Accept” when asked about permissions. These include situational context, transparency and flexibility.

In principle, there are two different ways to ask users the critical question. Either directly after installation and the first start of the app. Or when a specific function is called up within the app that requires specific access. In other words, the app asks for authorization for the camera when the camera function is used. The request is therefore made in a situational context. Of course, this only makes sense for apps that are structured accordingly. If I cannot even run an app without access to certain data (e.g. a messenger app without access to contacts), it makes sense to request this permission when starting the app.

“To be able to use this app optimally, you need …” Almost everyone who has ever installed an app knows this sentence. It is standard and most apps ask for access rights in exactly the same way. However, the relevant information is missing here. Users want to know why the app requires the relevant authorization. The most common ones are:

• Microphone
• Location
• Contacts
• Photos and videos

(Here you can find more information on what the accesses are often used for).

Information is essential, especially when the connection between the main function of the app and the authorization is not immediately clear. “The reasons for obtaining access permissions must be transparent and detailed,” says Maria. It is important to explain in as much detail as possible why the app needs access to the camera or why it is important that he or she shares the contacts. The more comprehensible these relationships are, the more willing users will be to grant access. Transparency is therefore essential.

If the app requires multiple accesses to different other apps, it may be useful to give users the option of switching individual permissions on and off themselves in the settings. It is important to point out which functionalities will only be available to a limited extent with which permissions. Of course, this only works if the app is designed in such a way that it continues to function even with restricted permissions, which is not necessarily the case for all applications. Of course, greater flexibility also means more “load” for users. To avoid having to click through ten individual access requests, the necessary authorizations should be reduced to a minimum – according to the motto “as little as possible but as much as necessary”.

It is worth paying particular attention to “permission handling” during app development and taking this topic into account as early as the conception phase. Something that we always take into account at Bitforge. In extreme cases, the right way to ask for permission determines whether the app is used or uninstalled again after downloading. Timing, information content and flexibility are key factors here. If you keep them in mind, you can give your users a relaxed click on “Allow access”.