On this Page
To prepare for Unity development for Android platforms, like the Oculus Go, you must set up the Unity Editor for Android development and install the Android SDK. The Oculus Mobile SDK is not required.
We recommend reviewing Unity’s Getting started with Android development for general information on Android development, but the essential setup steps are described below.
Once you have set up the Unity Editor for Android development, VR support is enabled by checking the Virtual Reality Supported checkbox in Player Settings. Applications targeting the Android Platform will then run on Gear VR.
Unity automatically applies orientation tracking, stereoscopic rendering, and distortion correction to your main camera when VR support is enabled. For more details, see Unity VR Support.
If you are already prepared for Unity Android development, you’re almost ready to begin mobile development.
Follow the instructions in the Oculus Go Device Setup sections of our Mobile SDK Developer Guide to prepare to run, debug, and test your mobile applications.
When configuring the Unity Editor for your project, you must select the device(s) that you’re going to target.
The Android SDK is required for mobile development with Unity. For setup instructions, Android Development Software Setup in our Mobile SDK Developer Guide. Most Unity developers do not need to install Android Studio or NDK.
Once you have installed the Standalone Android SDK tools, you may continue with this guide.
Once you have installed the Android SDK, you may wish to familiarize yourself with adb (Android Debug Bridge), a useful tool used for communicating with your Android phone. For more information, see Adb in our Mobile Developer Guide.
The Application ID is your app’s unique identifier. Add this ID to your Unity project by navigating to
Oculus / Platform / Edit Settings and populating the ID in the inspector.
You can retrieve your Application ID from the API page on the Oculus Dashboard.
Android applications are subject to more stringent limitations and requirements and computational limitations than Rift applications.
We strongly recommend carefully reviewing Mobile Development and Best Practices for Rift and Mobile in our Developer Guide to be sure you understand our performance targets and recommendations for mobile development. These sections contain important information that can help you avoid mistakes that we see frequently.
You may find it useful to preview applications using the Oculus Rift during development, but use caution when doing so. The rendering path for Android applications differs substantially from the rendering path used for Rift application previews and builds, and you may notice important differences in the look-and-feel and performance.
When developing for both Rift and mobile platforms, keep in mind that their requirements differ substantially. If you would like to generate builds for both PC and mobile from a single project, it is important to follow the more stringent mobile development best practices, as well as meeting the required framerate. This approach is not often taken in practice.
For information on Oculus tools to assist with mobile development, such as our Sample Framework or the Oculus Remote Monitor for performance debugging, please see Other Oculus Resources for Unity Developers.
For information on core VR development concepts, see the VR Development Best Practices.
Most Unity developers do not need to install the Oculus Mobile SDK. However, advanced developers may find it useful to review our Mobile SDK Developer Guide for insight into the underlying logic. Developers interested in the Android lifecycle and rendering path of Oculus mobile applications should review our documentation on VrApi. Mobile Best Practices and General Recommendations may also be of interest.
If you are interested in submitting an application to the Oculus Store, please see our Distribute Guide. We recommend doing so before beginning development in earnest so you have a realistic sense of our guidelines and requirements.