Oculus for Business Development Best Practices

This document shows you how to optimize the Oculus for Business application development process.

Local Development

To ensure you can sideload APKs and OBBs seamlessly, headsets used for development must be in development mode via the Device Manager before you can sideload the APKs.

Device Manager & Remote Installation

Device Manager is the official method for administering applications on Oculus for Business headsets. Device Manager allows you to remotely install, uninstall, and update applications all without physically accessing the headsets. In addition to remotely managing applications, you can use Device Manager to set up and manage MDM security measures for client headsets.

Migrating from Release Channels

Enterprise headsets migrating to the enterprise software need to be factory reset and provisioned with the enterprise software. For steps on factory resetting the headset, refer to our guide on how to perform a factory reset using the headset.

Warning: A factory reset on the headset will delete ALL data stored on the headset.

User Data Backup

If your application stores user data to the headset, please provide the user with options to either back up the data locally or to another service before they factory reset the headset.

Warning: A factory reset will delete ALL information on the headset. Unless the information is backed up to another location off of the headset, all information will be lost.

Please notify your end-users if your software requires them to set up a backup method to save their app data and preferences.

Cover Image

The APK icon is automatically used as the cover image. If there is no cover image in the Android Package, the Device Manager will create a template cover image using the app title in the manifest. If there is no app title in the manifest, the template cover image will use the title of the APK.


Please do not use launchers in your applications that may bypass the Oculus platform services. For more information, refer to the Enterprise Use Agreement. Instead of launchers, you can use Android intents for Deeplinking (https://developer.android.com/guide/components/intents-filters) to other applications installed on the headset.

Kiosk Mode

Kiosk Mode ensures that end users will only have access to intended use for trainings or enterprise enabled app experiences. Below we will explain how Kiosk Mode works and how to improve your users’ experience during Kiosk Mode.

  • If your application is intended to be controller-free, please implement a method for the user pause your application and resume it without losing their in-application progress.
  • You need to use Device Manager to change the app designated for Kiosk mode.
  • If the app crashes during Kiosk mode, the headset will restart and return to the app selected for Kiosk mode.
  • If the unit enters a crash loop, you will need to use Device Manager to remove the headset from Kiosk mode and restart the unit.

Turn Off Guardian

The Admin could use Device Manager to disable the Guardian on devices in particular groups of headsets. When Guardian is turned off, users interacting with seated or stationary apps can start using applications without extra steps. For more information, refer to our guide on how to turn off Guardian.

Managing headsets

The number of headsets you can provision at one time depends on the network infrastructure and environment used to provision the headsets. For additional information about how to manage your headsets, please refer to our headset management documentation.

Product Docs

Full product documentation is available for Device Manager and the Device Setup App on our support website.