Building VR apps for Meta Quest: a practical guide

Meta Quest headsets are standalone devices, so a VR app runs on the headset itself with no PC or cables. That makes them popular for training, education, events and games, but it also sets clear limits. Building VR apps for Meta Quest means designing for mobile-class hardware, for people's comfort and for Meta's store rules from the very first sprint.

Tools and engines

Most Quest apps are built with a game engine.

• Unity is the most common choice. Meta provides SDKs and samples for it, and Unity's XR tools support the OpenXR standard, which helps if you later target other headsets.
• Unreal Engine suits teams that need high visual quality and already know the engine, though it needs careful tuning for standalone hardware.
• WebXR runs VR in the headset's browser. It is quick to share through a link, but less capable than a native app.

For mixed reality, where digital content blends with a passthrough view of the room, Meta's SDKs add features such as scene understanding, spatial anchors and hand tracking. Check current documentation for exact capabilities on each headset model, as they differ between generations.

Performance comes first

On a flat screen, a dropped frame is a minor annoyance. In a headset, an unsteady frame rate can make people feel unwell. Your app must hold a steady frame rate that matches the headset's display, in every scene, on the oldest model you support.

The headset uses a mobile chipset, so treat it like a phone that is drawing two high-resolution images many times a second. Practical habits include:

• Keep draw calls low by combining meshes and sharing materials.
• Use baked lighting where possible, instead of many real-time lights and shadows.
• Limit transparency and post-processing effects, which are costly on mobile graphics chips.
• Watch texture sizes and polygon counts for every asset, not only hero objects.
• Use features built for headsets, such as fixed foveated rendering, which lowers detail at the edges of the view where the eye notices less.
• Profile on the device with Meta's performance tools, not only in the editor on a powerful PC.

Set a performance budget at the start of the project, and check against it every week. Fixing performance at the end is slow and expensive.

Comfort and safety

Comfort decides whether people will use your app for more than a few minutes. Motion sickness usually comes from a mismatch between what the eyes see and what the body feels.

Good comfort practice includes:

• Never move the camera without the user's input. Avoid forced camera shakes, sudden rotations or scripted motion.
• Offer comfortable movement options, such as teleporting and snap turning, alongside smooth movement for experienced users.
• Add a vignette that narrows the view during movement, as an option users can switch on.
• Support seated and standing play where it makes sense, and allow height adjustment.
• Keep text readable, with large, high-contrast type placed at a comfortable distance.
• Respect the play area. Design interactions that do not require people to walk into walls or furniture.

For training and enterprise apps, short sessions with natural breaks are often better than one long experience.

Interaction design

VR has no mouse and no touch screen, so interaction needs fresh thinking.

Some principles apply whichever input you choose. Make objects that can be grabbed look grabbable. Give instant feedback through sound, highlight or vibration when something is touched or selected. Place menus within easy reach, and avoid forcing people to look sharply up or down. Test with people who have never used VR, because first-time users behave very differently from developers.

Store submission and distribution

Public Quest apps are sold or listed through the Meta Horizon Store. Meta publishes technical and content requirements, often called Virtual Reality Checks, that cover areas such as performance, stability, the boundary and passthrough, account handling and store assets. Apps go through a review before release, and the process can take time, so plan for feedback and resubmission.

Before submitting, prepare:

• A build that meets the current technical requirements on every supported headset
• Store artwork, a trailer and a clear description in the formats Meta asks for
• A privacy policy and accurate data use information
• Comfort ratings and age ratings that reflect the experience honestly

Business apps for staff do not always need a public store listing. Meta offers options for managing headsets and distributing private apps to an organisation, and development builds can be installed on headsets in developer mode for testing. Check the current terms for whichever route you use.

Checklist before you build

• Which Quest models must you support, and will you test on the oldest?
• Is the core experience better in VR than on a screen?
• Have you set a performance budget for each scene?
• Which movement and comfort options will you offer?
• Controllers, hands or both?
• Will you publish on the store, or distribute privately?
• Who will create and optimise the 3D content?

Frequently asked questions

Can one VR app run on several Quest models?

Yes, in most cases. Build and test against the oldest model you support, since newer headsets generally have more processing power. Some features, such as colour passthrough, may only be available on certain models.

Should I use Unity or Unreal for a Quest app?

Unity is the more common choice for standalone headsets and has wide support from Meta. Unreal can deliver strong visuals but needs more optimisation work on mobile-class hardware. Our guide to choosing a game engine covers the trade-offs in more depth.

Do I need to publish on the Meta store?

Not always. Public consumer apps generally go through the store, while training and internal apps can often be distributed privately to an organisation's own headsets.

If you are planning a VR training tool, showroom or game for Quest, our AR and VR development team can help you scope it, keep it comfortable and get it ready for release.