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.
We're no longer accepting submission of 32-bit Oculus Quest apps. Any new or updated Oculus Quest application needs to be 64-bit. Please contact Oculus if you are unable to comply with this policy. Oculus Go and Gear VR apps will not be affected by this change.
This section will provide information on how to set up your Oculus Quest for running, debugging, and testing your application.
To begin development locally for Oculus Quest, you must enable Developer Mode in the companion app. Before you can put your Oculus Quest in Developer Mode, you need to have created (or belong to) a developer organization on the Oculus Dashboard.
To join an existing organization:
To create a new organization:
Enable Developer Mode
Then, to put your Oculus Quest 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 Oculus Quest. Note that developers should swap the provided USB cable with a USB3 cable.