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.
Your Oculus Go app must meet or exceed these guidelines to be considered for distribution on the Oculus Store. They are listed by category in the following sections.
The mobile test plan is the exact criteria we use to test your app during the technical review phase of the app submission process. It explains each requirement in detail, including steps to test and what the expected result is.
Download the test plan for Go/Gear:
These requirements ensure that your app meets all Go development requirements.
|VRC.Mobile.Go.1||Apps for Oculus Go must not require Android features that aren’t supported on Go.|
These requirements ensure that your app remains compatible with Oculus runtime libraries and you are mindful of Oculus recommended hardware specifications.
|VRC.Mobile.SDK.1||The app meets all graphics and performance guidelines running on supported mobile VR devices.|
|VRC.Mobile.SDK.2||You must use Oculus Mobile SDK version 1.0 or later, but version 1.5 or greater is recommended.|
|VRC.Mobile.SDK.3||Unity apps must be built with a supported version.|
|VRC.Mobile.SDK.4||Unreal Engine apps must be built with a supported distribution.|
These requirements ensure that your app meets all Android application packaging requirements.
|VRC.Mobile.Android.1||The application manifest must conform to the release manifest requirements.|
|VRC.Mobile.Android.2||The application must be signed with your unique digital certificate. All subsequent versions of your app must also be signed with the same certificate.|
These requirements ensure your app is responsive, performant, and able to render graphics at the quality expected for an Oculus Store app.
|VRC.Mobile.Performance.1||The app displays graphics in the headset at 60 frames per second.|
|VRC.Mobile.Performance.2||The app displays graphics without judder.|
|VRC.Mobile.Performance.3||The app must run for 45 minutes with typical usage without entering thermal throttling Power Save mode.|
|VRC.Mobile.Performance.4||The app renders without convergence errors or unusual distortion.|
|VRC.Mobile.Performance.5||The app renders without visible z-fighting or depth conflict artifacts.|
|VRC.Mobile.Performance.6||The app must either display head-tracked graphics in the headset within 4 seconds of launch or provide a loading indicator in VR.|
These requirements ensure your app functions according to Oculus Store standards.
|VRC.Mobile.Functional.1||The app runs and installs without crashing, freezing, or entering extended unresponsive states.|
|VRC.Mobile.Functional.2||The app must not lose the user’s data.|
|VRC.Mobile.Functional.3||The app must not leave the user stuck at any point in the experience.|
|VRC.Mobile.Functional.4||If your app requires Internet connectivity for its core functionality, notify users without an active Internet connection that one is required.|
|VRC.Mobile.Functional.5||The app must continue to download content if the user removes the headset or removes the device from headset.|
|VRC.Mobile.Functional.6||The app must reset the user’s orientation if the user removes the headset and puts it back on.|
|VRC.Mobile.Functional.7||The app must reset the user’s orientation if the user selects Reorient in Oculus Dash.|
|VRC.Mobile.Functional.8||Single player apps should pause when the user removes the headset or opens Oculus Dash.|
|VRC.Mobile.Functional.9||The app should not submit frames or accept input when the user removes the headset or opens Oculus Dash.|
|VRC.Mobile.Functional.10||Headlocked menus and UI elements are generally uncomfortable for the user and should be avoided.|
|VRC.Mobile.Functional.11||Apk filesize must be less than 1 GB, but can come with an expansion file up to 4 GB.|
These requirements ensure your app safeguards the privacy and integrity of Oculus and customer data.
|VRC.Mobile.Security.1||The app must perform an Oculus Platform entitlement check within 10 seconds of launch and exit the app if the check fails.|
|VRC.Mobile.Security.2||The app must request the minimum number of permissions required to function.|
These requirements ensure your app provides a user experience consistent with Oculus user interaction standards.
|VRC.Mobile.Input.1||If the app cannot be used without an external input device (e.g. gamepad or 3DOF controller), and no input device is detected when the app starts up, the app must warn the user to connect the necessary device.|
|VRC.Mobile.Input.2||The app must open Oculus Dash if the user long-presses the back button.|
|VRC.Mobile.Input.3||When the user presses the back button, the app must either go back one level in your UI or display a menu with an option to quit the app.|
|VRC.Mobile.Input.4||If the app supports both Gear VR touchpad and Gear VR Controller input, the app must let users switch between them at-will.|
|VRC.Mobile.Input.5||The app must use the built-in volume control UI when the user presses the volume buttons.|
|VRC.Mobile.Input.6||The app must detect if the 3DOF controller is set to left-handed or right-handed, and it must function equally well when used with either configuration.|
|VRC.Mobile.Input.7||The app should detect what device it’s running on and use the correct controller graphics and terminology.|
These requirements ensure your app meets the asset and content guidelines for shipping in the Oculus Store.
|VRC.Mobile.Asset.1||Logo must be on a transparent background.|
|VRC.Mobile.Asset.2||Store cover art images must have a clear logo without extraneous text, taglines, or banners.|
|VRC.Mobile.Asset.3||Store cover art must not include text in the top or bottom 20% of the image.|
|VRC.Mobile.Asset.4||Hero art must include the branding of the app centered in the image.|
|VRC.Mobile.Asset.5||Screenshots must be representative of the app and don’t contain any additional logos, text, or iconography.|
|VRC.Mobile.Asset.6||App description, screenshots, and videos must not include HMDs, controllers, or logos for other VR platforms.|
|VRC.Mobile.Asset.7||Trailer must not be longer than 2 minutes.|
|VRC.Mobile.Asset.8||Artwork asset text should not use a font smaller than 24 pt.|
|VRC.Mobile.Asset.9||If app is supported on both Gear VR and Oculus Go, any references in the app description and trailer should mention both devices.|