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.
Note: You are viewing the Unity version of this topic. To view this topic for native development, see Oculus Cross-Device Development with App Groupings (Native). To view this topic for Unreal development, see Oculus Cross-Device Development with App Groupings (Unreal).
You must choose the target Oculus device when you create an app page on the developer dashboard. This means that if you release an app that targets multiple Oculus devices, such as Rift and Go, you have two apps in the dashboard. By default, each of these apps would have their own platform settings.
App groupings enable Oculus cross-device development by sharing platform settings across all apps in a grouping. This can simplify management and enables you to easily deploy changes across multiple apps.
Following is a list of platform features that can be shared across apps in app groupings:
When you create an app, by default it is put in an app grouping of the same name. This default grouping has the same platform settings as the app it contains. To share platform services, you can create new groupings and move apps from their default group into a group with other apps.
A new grouping does not contain any predefined settings, and is easy to create.
When you have created an org and added an app:
The following image shows an example:
The App Groupings page lists all apps for an organization by group. You can easily move apps from one grouping to another on this page.
Note: Be careful when moving apps that are already in-use. However, you can move the app back to its old grouping if necessary.
You can easily change the settings for an app grouping.