The Oculus dashboard plays a key role in the lifecycle of your Oculus application. The dashboard lets you distribute builds to testers and also serves as the portal for the review processes your app must go through for general distribution in the Oculus Store.
It is important to us that you know what to expect when you submit an app for us to distribute through the Oculus Store. The time and effort you put into your app is appreciated and we want to provide a fair and transparent path to success.
Successful apps go through phases of design, development and testing. When you submit your app, its content and performance will be evaluated before it can be released to the public. Once all aspects of your app meet our requirements, it can be published to the Oculus Store. The following image demonstrates the typical app lifecyle.
There are baseline elements that VR apps must incorporate and achieve to be ready for consumers. To help your apps be successful, we provide design guidance and set content and technical requirements that apps must meet before they are distributed through the Oculus Store. For our app design guidance see VR Best Practices and the Content Guidelines.
You also should review the technical and content standards in our Store Review Policies before you start development. Your app must meet these standards to be published in the Oculus store and they help us ensure a great user experience for Go, Gear VR and Oculus Rift owners.
You can start your Oculus development by creating an app page in the developer dashboard. For information on how to create the page, see Creating an App Page. Then, develop your VR app using our platform solutions and SDKs. You will need to understand concepts like the platform entitlement check, and how to handle the back button correctly in a mobile app. For more information about how to develop for Oculus and the resouces available, see the developer documentation.
You can submit builds to your app page on the Oculus dashboard using of four default channels. The Alpha, Beta, and Release Candidate channels enable you to give external users access to your app for testing purposes.
Use the Store channel when you are ready for Oculus to review your app. For more information about submitting builds, see Release Channels.
However, before you submit your app for review, you should complete some readiness testing.
You can also test store readiness of Rift apps using the VRC Validator Tool.
When you think your app meets all of the store requirements, upload a build to the Store channel and submit it for review.
The store review process checks whether your app meets all the minimum technical and content standards required for consideration. The technical requirements are documented in the Virtual Reality Check Guidelines.
If your app fails its initial technical review, we want to make sure you know why, and what to do next. You will recieve a detailed report about your app, showing you exactly which technical requirement(s) you’re missing, and pointing you toward links in our Developer Center where you can learn about how to approach fixing the issue. You are then welcome to resubmit the app.
After an app successfully passes technical review, it enters content review, where we evaluate the app for its overall completeness, polish, and value. We expect games, videos, virtual tours, and other kinds of apps to be engaging, interesting, or useful.
The content in the Oculus Store is carefully curated. A wide range of tastes and viewpoints are taken into consideration when apps are reviewed for publication. Essentially, we try to put ourselves into our customer’s shoes and discern what people will enjoy and engage with.
For more information, see Content and Design Guidelines.
If your app passes the technical review and content review stages it becomes eligible for inclusion in the Oculus Store and is then passed on to our publishing review team for Oculus Store classification and categorization.
After publishing review is complete, you will be able to distribute your app through one, or both, of the following methods: