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.
You can use Device Manager to remotely install apps on to your headsets. Instead of uploading your app to the Facebook servers for distribution, customers and developers have the option to host content on their own servers and configure their headsets to fetch content from custom locations. The customer and developer need to determine the hosting configuration and set up their headsets accordingly.
To manage applications, navigate to your App Library. Here, you can add apps to your library, after which, can be deployed to your fleet of headsets.
To add an app to your library, in the top right of Device Manager, click on the blue Add App button.
This is your application’s name in Device Manager. This title is used to assist you in managing your applications.
The next set of information provides your headsets with your application’s configuration and address on the server. Some of the information fields are required to install the app properly on your headsets. The other information fields enhances the application data transfer from your specified address on your server to your headset.
This is the server address where your app is hosted. You can test this URI by visiting the address in your browser. A valid URI will trigger the browser to automatically download your app binary. Please confirm that your headsets can also connect to this URI with their configured WIFI network.
NOTE: The current software version does not support URIs with any percent-encoded characters, including whitespace. This limitation will be removed in a future release.
Custom Request Headers (Optional)
You can use custom request headers to configure the HTTP requests used to download the app binaries. Custom Request Headers can be used to include an Authorization HTTP header in Device Manager to support password-protected web servers. If Custom Request Headers are defined, your headsets will include all of the headers in all application download requests.
You can use a SHA-256 hash to provide additional security for your application. It ensures that there were no tampering, transmission, or web server errors during the download process. The hash field requires the hexadecimal representation of the SHA-256 digest of the app binaries.
Oculus suggests using a hash to configure Device Manager remote installs for your app. It is recommended for communicating with web servers that do not use SSL protocols, but it is not a mandatory requirement.
Launch Intents (Required)
You can use Android launch intents to specify a location in an application that will be accessed when you launch the app. Launch intents can be used as deep links within your app. We require you to provide at least one launch intent, but you can integrate multiple launch intents you can select when you deploy the app to the headsets.
Once you’ve added your application to the App Library, it’s time to deploy it to your headsets. From the Enable App on Devices menu that is now available, you’ll see the option to deploy your application. Here, you can choose to enable your application on all of your devices or a specific group of headsets.
Your app will be installed the next time your headset or group of headsets connect to the Device Manager tool to receive new configurations.
After an app is added to your App Library, you can deploy it at any time to an individual headset or group of headsets.
To deploy to an individual headset, from your Device Manager, click on the Device Fleet tab, and select one of your devices. From here, click on the Apps tab for the selected individual device. The Apps tab will list the applications you can enable from your App Library.
Your app will be installed the next time your application connects to the Device Manager tool to receive a new configuration.
Similarly, you can deploy an app from your App Library to a group of headsets by navigating to the selected group and selecting the app from the app panel.
Once you have added your application to your app library and deployed it to a group of headsets, you can update your application to a newer version in your app library:
The new application will be deployed to your headset upon the next configuration update.
NOTE: If you were to create a new app in your app library for the update, the installer will replace the old app with the new one, but you will see multiple “versions” of this application in the Device Manager which will now all point to the same app on the headset. To remove these apps, the obsolete apps in the Device Manager tool will need to be removed.