Meta Quest is the dominant VR platform with an estimated 70-75% market share in consumer and enterprise VR. Quest 3, launched in late 2023 and now the standard device in 2026, brought full-color passthrough, a faster Snapdragon XR2 Gen 2 chip, and mixed reality capabilities that blur the line between VR and AR. Quest Pro remains the enterprise choice for higher visual fidelity and face/eye tracking.
If you're building a VR application — whether it's a game, training simulation, enterprise tool, or social experience — Quest is almost certainly your primary target platform. This guide covers the technical requirements, SDK landscape, performance targets, and store submission process.
Quest 3 vs Quest Pro: Hardware Comparison
Understanding the hardware constrains every design and engineering decision.
Quest 3 - **Chipset:** Snapdragon XR2 Gen 2 - **RAM:** 8 GB (5-6 GB usable by apps) - **Display:** 2064 x 2208 per eye, LCD - **Refresh rates:** 72Hz, 90Hz, 120Hz - **Passthrough:** Full-color, stereoscopic - **Tracking:** Inside-out 6DoF, hand tracking v2.2 - **Storage:** 128 GB / 512 GB - **Price:** ~$500 - **Target audience:** Consumer and light enterprise
Quest Pro - **Chipset:** Snapdragon XR2+ Gen 1 (slightly slower than Quest 3) - **RAM:** 12 GB (8-9 GB usable) - **Display:** 1800 x 1920 per eye, mini-LED with local dimming - **Refresh rates:** 72Hz, 90Hz - **Passthrough:** Full-color, higher quality than Quest 3 - **Tracking:** Inside-out 6DoF, face tracking, eye tracking - **Storage:** 256 GB - **Price:** ~$1,000 - **Target audience:** Enterprise, professional
For most projects, target Quest 3 as the baseline. Quest Pro adds face and eye tracking (useful for avatars and social presence) and more RAM (useful for complex enterprise apps), but Quest 3's faster GPU means better rendering performance.
The Meta XR SDK Stack
Meta's SDK landscape has consolidated significantly since the Oculus days. Here's what you need in 2026:
Meta XR All-in-One SDK (Unity)
The primary integration point for Unity developers. This replaces the older Oculus Integration package and bundles: - Meta XR Core SDK — headset and controller tracking, passthrough, spatial anchors - Meta XR Interaction SDK — hand tracking, controller interactions, poke, grab, ray - Meta XR Platform SDK — user identity, entitlements, achievements, leaderboards - Meta XR Audio SDK — spatial audio with room modeling - Meta XR Haptics SDK — controller haptic feedback design
Install via Unity Package Manager. The SDK requires Unity 2022.3 LTS or Unity 6.
Unreal Engine Integration
Meta provides the Meta XR Plugin for Unreal Engine 5.3+. It covers the same ground as the Unity SDK but with fewer community examples and tutorials. If your team is Unreal-native, this works fine. If you're choosing between engines for Quest development, Unity has a much larger ecosystem of Quest-specific resources.
Native Development (C/C++)
For maximum performance control, you can build directly with the Meta Quest Native SDK. This is used by studios building custom engines or performance-critical applications (high-end games, real-time simulation). The tradeoff is development speed — expect 3-5x longer development timelines compared to Unity.
Performance Requirements: The Non-Negotiable Numbers
VR has hard performance requirements. Miss them and users experience motion sickness — not just a bad experience, but a physical health issue.
Frame Rate Targets
- -72fps: Absolute minimum. Below this, most users will feel discomfort within minutes.
- -90fps: The recommended target for most applications. This gives you 11.1ms per frame.
- -120fps: Available on Quest 3. Noticeably smoother, but the 8.3ms frame budget is tight on mobile hardware. Reserve for visually simple apps (social, UI-heavy, casual games).
Frame Budget Breakdown (at 90fps = 11.1ms)
- -CPU game logic: 3-4ms
- -CPU render preparation: 2-3ms
- -GPU rendering: 4-6ms
- -Headroom for spikes: 1-2ms
If your GPU time exceeds 8ms consistently, you need to reduce draw calls, lower texture resolution, simplify shaders, or reduce polygon counts.
Memory Budget
Quest 3 gives you about 5.5 GB of usable RAM. Recommended allocation: - Application: 2-3 GB - Textures: 1-1.5 GB - Audio: 200-400 MB - System reserve: 1-1.5 GB
Exceeding memory limits causes the OS to kill your app without warning. Profile memory usage with Meta's OVR Metrics Tool and Unity's Memory Profiler.
Thermal Throttling
Quest 3 runs on a mobile chip with passive cooling. Sustained high GPU/CPU usage triggers thermal throttling — the system reduces clock speeds to prevent overheating, dropping your frame rate below target. Design for 80% of peak performance as your sustainable ceiling.
Hand Tracking Development
Hand tracking is no longer a novelty — it's an expected interaction method. Quest 3 supports hand tracking v2.2 with improved accuracy and lower latency.
Design Guidelines for Hand Tracking
Use the Meta Interaction SDK. Don't build custom hand tracking from scratch. The Interaction SDK provides poke (touching surfaces), grab (picking up objects), and ray (pointing at distant targets) interactions with tested UX patterns.
Design for imprecision. Hand tracking is less precise than controllers. Make interactive elements at least 6cm x 6cm in virtual space. Add generous hit boxes and visual feedback for hover states.
Support both input methods. Never build a Quest app that only supports hand tracking. Controllers are more precise, less fatiguing, and required for many gameplay mechanics. Detect input method dynamically and adapt your UI.
Avoid sustained arm raises. The "gorilla arm" problem is real. If users need to interact above shoulder height for more than 30 seconds, they'll fatigue. Place primary interactions in the comfort zone (waist to chest height, within arm's reach).
Mixed Reality Development
Quest 3's full-color passthrough enables mixed reality (MR) applications — apps that blend virtual content with the physical environment. This is the fastest-growing category on the Quest Store.
Passthrough and Scene Understanding
The Quest OS provides: - Passthrough rendering — real-time camera feed composited behind virtual content - Scene Model — the system's understanding of room geometry (walls, floor, ceiling, furniture) - Spatial Anchors — persistent points in physical space where virtual content can be placed - Plane Detection — real-time identification of horizontal and vertical surfaces
MR Design Patterns
Room-scale experiences: Use Scene Model data to spawn virtual content that respects room boundaries. Enemies that come through walls, portals on detected surfaces, virtual objects on real tables.
AR overlays: Render virtual information anchored to physical space — instructions overlaid on real machinery, navigation arrows on real floors, virtual whiteboards on real walls.
Transitional experiences: Start in passthrough, gradually transition to full VR. This reduces disorientation and is the recommended UX pattern for enterprise applications.
Quest Store Submission Process
Getting on the Quest Store is significantly harder than publishing a mobile app. Meta curates aggressively — estimated acceptance rate is 15-25% for first submissions.
Submission Requirements
1. Technical Review Checklist (TRC): Meta provides a 100+ item checklist covering performance, input handling, comfort, accessibility, and platform integration. Every item must pass.
2. Performance certification: Your app must maintain target frame rate (72/90/120fps depending on your selection) across all supported scenarios. Meta tests on reference hardware.
3. Comfort rating: Self-certify your app as Comfortable, Moderate, or Intense based on locomotion and camera movement. Misrating results in rejection.
4. Entitlement check: Your app must verify the user owns it via the Platform SDK before allowing access. No entitlement check = automatic rejection.
5. Content review: Meta reviews your app for content policy compliance, quality standards, and market viability.
App Lab: The Alternative
If your app doesn't meet Quest Store curation standards, App Lab provides distribution without store listing. Apps are accessible via direct link or search. App Lab has a lower quality bar but receives significantly less organic traffic.
Enterprise Deployment
For enterprise apps that don't need the public store, Meta Quest for Business provides: - Device Management: Remote configuration, app deployment, kiosk mode - Private App Distribution: Deploy apps to managed devices without store approval - Fleet Management: Monitor device health, battery, and usage across locations
Cost Breakdown for Quest Development
Development Costs
- -Simple VR app (single environment, basic interactions): $80K-150K
- -VR game (multiple levels, polished mechanics): $150K-500K
- -VR training module (one scenario, assessment, analytics): $100K-300K
- -Enterprise MR application (scene understanding, spatial anchors): $150K-400K
- -Full VR platform (multi-module, fleet deployment, backend): $400K-1.2M
Hardware Costs (Per User)
- -Quest 3 (128 GB): $500
- -Quest 3 (512 GB): $650
- -Quest Pro: $1,000
- -Elite Strap / comfort accessories: $50-100
- -Quest for Business license: $180/year per device
Ongoing Costs
- -Store maintenance (OS updates, SDK updates): $2,000-5,000/month
- -Content updates (quarterly): $15K-50K per update
- -Backend infrastructure (if applicable): $500-5,000/month depending on scale
Quest vs Apple Vision Pro Development
Vision Pro launched a new spatial computing paradigm, but the development economics are very different:
| Factor | Quest 3 | Apple Vision Pro |
|---|---|---|
| Device cost | $500 | $3,500 |
| Installed base | 20M+ | ~1M |
| Dev language | C# (Unity) or C++ | Swift/SwiftUI + RealityKit (or Unity PolySpatial) |
| Store acceptance | Curated (15-25%) | Curated (similar) |
| Enterprise adoption | High | Growing |
| MR capability | Good (720p passthrough) | Excellent (4K passthrough) |
| Development cost | Lower (larger talent pool) | Higher (SwiftUI/RealityKit is niche) |
For most projects in 2026, build for Quest first. Port to Vision Pro if the business case justifies the additional development cost ($50K-150K for a port, depending on complexity).
How WODH Builds for Quest
Our XR Studio has shipped 12+ Quest applications across gaming, enterprise training, and mixed reality. We develop in Unity with the Meta XR SDK, handle performance optimization for the mobile GPU constraints, and manage the full store submission process including TRC compliance.
From HAKI's VR scaffolding training to interactive product experiences, we build Quest apps that pass Meta's certification on the first or second submission — not the fifth. If you're planning a Quest project, we can scope it and provide a technical architecture review before development begins.