Understand permissions for XR

Applicable XR devices

This guidance helps you build experiences for these types of XR devices.

Learn about XR device types →

Learn about XR device types →

Just like apps on mobile devices and other form factors, some capabilities offered by XR apps require your app to declare permissions in your app's AndroidManifest file. In the case of dangerous permissions, your app may need to request runtime permissions. Read Permissions on Android and permission best practices for more in-depth information.

The following permissions can be used by XR apps. All of the permissions in this section are considered dangerous permissions, so you must declare them in your app manifest and request them at runtime.

android.permission.EYE_TRACKING_COARSE

Representing the user's eye pose, status, and orientation, such as for use with avatars. Use this permission when low-precision eye tracking data is needed.

android.permission.EYE_TRACKING_FINE

Eye gaze for selection, input, interactions, and eye-tracked foveated rendering.

android.permission.FACE_TRACKING

Tracking and rendering facial expressions.

android.permission.RECORD_AUDIO

Recording audio input, such as for audio-driven face tracking data sources.

android.permission.HAND_TRACKING

Tracking hand joint poses and angular and linear velocities; using a mesh representation of the user's hands.

android.permission.BODY_TRACKING

Tracking body joint poses and skeleton proportions.

android.permission.SCENE_UNDERSTANDING_COARSE

Light estimation; projecting passthrough onto mesh surfaces; performing raycasts against trackables in the environment; plane, image, marker, QR code, mesh, and object tracking; persistent and shared anchors.

android.permission.SCENE_UNDERSTANDING_FINE

Depth textures; scene meshing; cubemap light estimation; depth raycasting and spatial annotations.

android.permission.ACCESS_FINE_LOCATION

Precise Earth-relative location and orientation for Geospatial tracking and anchors.