Release for AR/VR Developers
XR release is the final stage of getting an app to users: building for the target platform, passing store requirements, handling privacy and permissions, and distributing through stores such as the Meta Quest Store, Google Play or the App Store. It also includes testing on real devices and planning updates.
Stage: Performance and Release · Part of the AR/VR Developer roadmap · Last reviewed 19 November 2026
What to learn in Release
- Produce a signed Android build for a standalone headset or phone
- Test on real hardware across different devices, lighting and room sizes
- Prepare store assets, descriptions and age ratings and a privacy policy
- Request camera, microphone and spatial data permissions with clear explanations
- Plan versioning and updates after launch based on crash and usage data
Release interview questions
Why is testing on a real device essential for XR?
Editor playback hides problems that only real hardware shows, such as frame drops, tracking loss in poor lighting, comfort issues and controller quirks. A scene that looks fine on a desktop can be unusable on a mobile chipset, so test early and often on target devices.
What privacy concerns apply to AR and VR apps?
XR apps can access cameras, microphones, room scans and sometimes eye or hand tracking, which are sensitive. You should request only the permissions you need, explain why, avoid storing raw sensor data unnecessarily, and publish a clear privacy policy that stores require.
Where Release fits in the AR/VR Developer roadmap
Release belongs to the Performance and Release stage (advanced level). Ship it.
Other units in this stage
Back to the full AR/VR Developer roadmap