Oculus Go Development

On 6/23/20 Oculus announced plans to sunset Oculus Go. Information about dates and alternatives can be found in the Oculus Go introduction.

Oculus Quest Development

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.

Oculus for Business Self-Hosted Apps

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 retrieve 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.

Adding Apps to Your Library

To add an app to your library, in the top right of Device Manager, click on the blue Add App button.

Display Information

This is your application’s name in Device Manager. This title is used to assist you in managing your applications.

Self-hosted app manager information

App Binary Information

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.

  • Name (Required) The name of your application. This name will only be used in the Device Manager.
  • Link to App File (Required) 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.
  • Hash (Optional) 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.

Expansion Files (Optional)

For expansion files, You’ll populate the same app information as the main app. You’ll be asked to identify if the expansion file is an Application OBB Path to be downloaded or an User Shared Storage file.

Self-hosted app manager expansion file information

Deploying Your OFB App to Device(s)

The Oculus for Business support article Using Device Manager details how to deploy, manage, and update apps on your OFB device fleet.