We’ve heard from our developer community that it can be challenging to find the tool or feature for your use-case on developer.oculus.com. To resolve these challenges, we’re launching a new documentation architecture to enable a more user-friendly, curated, experience throughout the website.
This new architecture is device-centric, organizing the content by your preferred development platform: Unity, Unreal Engine, Native or Web. Some information has moved, like the pages that were previously in the Audio SDK, Platform SDK, and Avatar SDK guides. Development information for these SDKs are now contained in Unity, Unreal Engine, and Native.
We’ve also provided a device selector at the top of each page to filter only information for the desired Oculus development device, like the example below.
On your initial visit, you’ll be prompted to select your target device for development. This module (show above) will be displayed throughout the documentation section of the website, allowing you to toggle between Oculus devices and displaying information based on your selection. Your preferred device will persist as you navigate between pages and sessions unless you choose to browse logged out and in incognito mode.
Some content is not supported for all devices, and content may differ depending on your selection. For example, Haptics are only supported on Oculus Quest and Rift, so the device selector will not allow you to choose Oculus Go and shows as disabled in gray.
If you navigate to a page that is not supported for the device you’ve selected, you’ll be prompted to change your device or navigate elsewhere.
As always, we welcome your feedback. Use the widget at the bottom of any documentation page to give us a thumbs up or down.
Documentation URLs across the site have changed. We’ve done our best to add redirects to the new location on the site, but please update any bookmarks that you may have.
We hope this new architecture enables you to locate development information on developer.oculus.com with ease. If you have any follow up questions about this update, feel free to post a comment below, or reach out through the Developer Contact Us Page!