Oculus Quest and Quest 2 deliver the freedom of wireless, standalone VR with the industry leading power and performance to drive your next immersive app. Both of these devices include spatially tracked controllers, integrated open-ear audio, and support for Oculus Link which enables users to access their Oculus Rift library of apps from their gaming compatible PC.
This overview will help you kick off your next VR development process, including background information on Quest and Quest 2, materials for learning performance optimization techniques, and background on the Oculus Store submission policy. We look forward to experiencing the new worlds, and realities you create with these all-in-one VR systems.
Oculus Quest and Quest 2 deliver the freedom of 6DOF VR, the power and flexibility of a Qualcomm Snapdragon processor, and the same developer software platform. Features such as Guardian, Passthrough+, hand tracking and our redesigned Universal menu are also available on both headsets.
While there are similarities, we are especially excited about the potential that Quest 2 will bring to VR audiences everywhere with even more power, higher resolution, and a more affordable price. See below for a few of the key differences between these headsets, highlighting what makes Quest 2 a premium VR device for you to design, develop and distribute your next VR app.
This process is resulting in elevated developer success and player satisfaction on the Quest platform. We look forward to working with you and your team to deliver inspired games and apps with this mobile VR technology.
Want to learn more about Quest 2? Check out the Quest 2 announcement blog post for even more about the headset, along with an initial set of developer FAQs.
Quest and Quest 2 feature a mobile chipset running Android, and include its own set of development processes and best practices. Some of these nuances may be new for those who specialize in console or PC engineering, so to start developing for this 6DOF, all-in-one VR system, we recommend the following resources for Unity, Unreal, and Native development.
To ensure developer success and optimize the store experience for VR consumers, the Quest Store Policies align with VR player expectations that Quest and Quest 2 apps have a certain amount of depth and polish. These policies will help you to focus your time and resources, while enabling VR players to be confident in the quality of games throughout the Quest library.
It’s important to note that with these policies, you are required to provide a concept pitch document, showing the quality of the concept, probability of market success, and adherence to the Oculus Content Guidelines. This document is an opportunity for you to show how amazing your game will be, and how it will speak to the Quest audience. For inspiration, here is an example concept doc for an undeveloped game titled Oil Rig.
Once approved, you will receive non-public development resources and access to submit your app to the Quest store. Be sure to also review the Quest Virtual Reality Checks (VRCs) and Developer Policies which are required before officially publishing your app. It’s recommended that these are taken into consideration early in your development process.
For more information on these policies, commonly failed VRCs and other insights about submitting your app for publishing on the Oculus store, be sure to review the Store Submission Guide. The submission process results in elevated developer success and player satisfaction on Quest and Quest 2. We look forward to working with you and your team to deliver inspired games and apps with this mobile VR technology.
If you are new to VR development, it’s important to note that compared to 2D game and software engineering, performance optimization is essential to delivering a successful app. Missed frames can be moderately tolerated in mobile and console games, but in VR, dropped frames can cause significant discomfort, potentially deterring a user from experiencing your app all together.
As opposed to developing for PC VR, optimizing for the mobile chipset requires different planning and tactics for optimization. Keep this in mind as you plan to develop for Quest and Quest 2, as best practices like minimizing draw calls and shader complexity, thorough frame analysis and efficient use of expansion files are all important to the success of your app.
Recognizing that the optimization process is both essential and (can be) time consuming, we have created a number of tools, resources, guides and videos to ensure your success:
See below for a detailed set of technical specs for the Oculus Quest and Quest 2. If you haven’t already, check out the Get Started Page for how these compare with the Rift S.