Patterns – Permissions

Permissions

Permission requests should be simple, transparent, and understandable. When requesting access, apps should ensure that either the feature itself or an explanation provided makes it clear why a permission is needed. Since Android 5.0 (Marshmallow), user permissions are requested at runtime.

Watch permissions Expand and collapse content An arrow that points down when collapsed and points up when expanded.

When Android Wear needs to grant permission to a watch app, a dialog is displayed asking the user to accept or reject that permission.

Apps should request permissions at the time and place that makes it clear why the permission is needed.

Apps may request permissions:

  • Upon launch
  • After providing information about a specific permission
Watch permissions

Example of permissions for a fitness app

Multiple permissions

If an app or watch face requires more than one permission at a time, the permission requests appear sequentially, one after the other.

Phone permissions Expand and collapse content An arrow that points down when collapsed and points up when expanded.

Mobile device permissions

When an app requests a permission, the app must direct the user to accept that permission on their mobile device.

On the mobile device, more information may be provided about the permission. Two buttons should be included for the permission: one for granting it, and one for denying it.

Phone permissions example 1

Example of an app requesting a permission on a watch and directing the user to the mobile device to accept the permission.

Watch permissions

When an app requires a watch permission, the app must direct the user to accept that permission on the watch.

Phone permissions example 2

Example of an app on a mobile device directing the user to accept a permission on the watch.