Permission Primer screen schema.

Keeping on the theme of the new account experience, commonly users are asked right away to grant security permissions to their notifications, camera, and more. Without being told how these permissions help the user and give them better experiences, the rate of granting permission is low. Furthermore, one of our design experience values is Contextual and Bespoke. We should adapt to the users situation and be aware of where they are in the journey.

To better understand app permissions, and communicate where and what to do, I put together information architecture and a user flow of the current app permissions.

Next I documented the current permission experience, and took note of the differences between platforms. This allowed everyone to see what the first time experience was and how app permissions was not being handled with care or sensitivity. Doing this would make us more Personable and Transparent, which were our design experience principles.

Next I laid out all the permission types with their updated app permission experiences. One example of an app permission experience principle is to ask for permission when it’s contextually relevant and required for the task the user doing.

I identified what current notification types we had, and mocked them up next to their respective place in the app journey.