In Context: Permissions with the Hover SDK, part II

Our four permissions explained

As we explored in part I of this post, though a bit arduous, our permissions are necessary to give people a seamless in-app transaction experience. We applied the design principles from our UX research and have seen great improvements in user satisfaction.

Below is the default permission flow provided by the Hover SDK’s PermissionActivity. If any permissions have already been granted then they will be excluded from the summary list and the dialog requesting the permission from the user will not show. If you don’t customize these permissions, these screens will be shown to end users when they first run your app.

Permissions summary

This will only list permissions not yet granted and will appear on an app’s first run by default.

Phone permissions

This dialog is provided by Android. Text and design cannot be changed.

SMS permissions

This dialog is provided by Android. Text and design cannot be changed.

Overlay simulated

This is a simulated permission meant to let the user know what to expect in the following settings screen. This will only show on devices running Android v6.0–6.4

Overlay toggle

The user must press the toggle in the top right and then press back to return to the app. The text on this screen is provided by Android and cannot be changed. This will only show on devices running Android v6.0–6.4

Accessibility simulated

This is a simulated permission meant to let the user know what to expect in the following settings screen. Pressing ‘open settings’ will take the user directly to the following accessibility settings list page.

The following is an example of what your users can expect when turning on Accessibility for your app. Because these screens are controlled within the device settings, most of them cannot be customized.

Accessibility list

The user must find your app in the list and choose it.

Accessibility toggle

The user must press the toggle in the top right which will show the following confirmation dialog. The text on this screen is customizable.

Accessibility confirm

Once the user presses ‘OK’ they will automatically be taken back to your app and the Permission Activity will complete with RESULT_OK.

Now that we’ve gone through all permission screens in detail, we will explore how these permissions would appear in the context of an app in part III.