Meta is looking for great WebXR content to feature on Browser’s New Tab Page.
WebXR Submission Form
If you have an experience you would like to feature on the New Tab Page, use our WebXR Submission form to submit your feature for consideration.
This page contains the general criteria we’ll apply when determining which experiences to feature on the New Tab Page. We change or rotate what content we feature in order to ensure we’re showing fresh, relevant, and diverse content for Browser users. Meeting the technical criteria below is not a guarantee your experience will be featured.
We only feature direct links to individual VR experiences as opposed to directories of VR experiences.
You must own or otherwise have rights to the content/experience you are submitting and have the authority to grant Meta permission to feature the experience, including any assets or descriptions you provide to Meta. Your content/experience must not infringe upon or violate the rights of any third party.
We prefer experiences that provide unique or differentiated value to users. We generally do not feature tech demos that don’t provide meaningful entertainment or utility.
Content should be appropriate for all ages 13 and older.
Hand tracking enabled experiences should provide an easily discoverable UI option to exit WebXR to return to the browser.
If an exit option is not made available in the experience’s UI, then the experience must render a full hand model (e.g. including fingers and all joints) such that users can easily see their hands to perform the system gesture to exit WebXR.
Technical Requirements
Meeting the following selection of Quest Virtual Reality Check (VRC) Guidelines is strongly encouraged and failing to meet these will likely result in not being featured on the New Tab Page:
VRC.Quest.Performance.1 - The experience must run at 60Hz or faster on Quest 1 & 2 (recommended 72Hz on Quest 1, 72Hz+ on Quest 2).
VRC.Quest.Performance.3 - The experience must be responsive within 4 seconds of entering VR or show a loading indicator.
VRC.Quest.Functional.1 - The experience runs without crashes, freezes, or extended unresponsive states.
VRC.Quest.Functional.3 - The experience must not leave the user stuck at any point in the experience.
VRC.Quest.Functional.5 - The experience must respond to the HMD’s positional tracking as well as orientation.
VRC.Quest.Input.3 - In-application hands and controllers should line up with the user’s real-world counterparts in position and orientation as closely as possible.
VRC.Quest.Input.8 - For applications that support hand tracking, the system gesture is reserved, and should not trigger any other actions within the application.
Technical Recommendations
Meeting the following VRCs are also recommended as best practices: