The site has a new content architecture. We've added the ability to select your development device to show device-specific content. Please read our blog post Oculus Developer Center Update: Device-centric Documentation Architecture for more information.
All Oculus Quest developers MUST PASS the concept review prior to gaining publishing access to the Quest Store and additional resources. Submit a concept document for review as early in your Quest application development cycle as possible. For additional information and context, please see Submitting Your App to the Oculus Quest Store.
This topic shows how to set up an Oculus Android device for running, debugging, and testing applications. The currently supported Oculus devices that run Android are Oculus Quest and Oculus Go.
Note: To set up an Oculus Rift for development, see the Rift Native SDK documentation.
To begin development locally, you must enable developer mode for the Oculus device in the companion app on your mobile phone. Before you can put your device in developer mode, you must belong to (or have created) a developer organization on the Oculus Dashboard. If developing on Windows, you will also need to install drivers to use Android Device Bridge (ADB).
Joining or Creating an Organization
To join an existing organization, follow these steps:
To create a new organization, follow these steps:
Enable Developer Mode
Once you belong to a developer organization, follow these steps to put your device in developer mode:
Developer Mode is intended for development activities such as running, debugging and testing applications. Other activities could result in your account being limited, suspended or terminated. For more information, see Oculus Developer Content Guidelines.
Install the Oculus ADB Drivers (Windows only)
If you are going to be pushing builds from a Windows machine, you’ll need the Oculus ADB Drivers.
.inffile and select Install.
Once complete, you’ll be able to use Android Debug Bridge (ADB) to push builds to your device.