Meta Quest Development: From Zero to Published App

Meta Quest is the dominant standalone VR platform with millions of active users. The Horizon Store generates hundreds of millions in annual revenue, and the App Lab distribution channel gives independent developers a frictionless path to getting their app in front of Quest users. Building for Quest is one of the most direct paths to shipping a VR product that real people use.

This guide walks through the complete Meta Quest development workflow: setup, Unity integration, Meta's SDK ecosystem, building core interactions, optimizing performance for the Quest hardware, testing, and shipping your app.


Development Environment Setup

Step 1: Developer Account

Register at developer.oculus.com. Join or create an organization (even a solo developer organization works). This enables the Developer Mode toggle in the Meta mobile app that allows sideloading and ADB debugging.

Step 2: Enable Developer Mode

In the Meta mobile app, go to Headset Settings → Developer Mode → toggle on. This allows your PC to communicate with the headset over USB (via Android Debug Bridge, ADB).

Step 3: Install Meta Quest Developer Hub

Meta Quest Developer Hub (MQDH) is the companion desktop app for Quest development. It handles sideloading APK builds, launching apps, capturing logs, and performance profiling. Download free at developer.meta.com.

Step 4: Unity Setup for Quest

- Install Unity 2022 LTS with Android Build Support module - Install Meta XR SDK via Meta's Unity Package Registry or Asset Store - Configure Project Settings: Platform = Android, ARM64, IL2CPP, API Level 29+ - Add the OVRManager component to your XR Rig for Quest-specific features ## Meta XR SDK Core Components

OVRManager

OVRManager is the central controller for Quest-specific settings: tracking origin type, hand tracking support, passthrough camera access, boundary system settings, and performance overlay. Every Quest project needs OVRManager in the scene.

Meta Interaction SDK

The Meta Interaction SDK provides polished, production-tested interaction components: GrabInteractable, DistanceGrabInteractable, PokeInteractable for finger poke buttons, and RayInteractable for UI. These build on the XR Interaction Toolkit with Quest-specific optimizations.

Hand Tracking

Meta Quest 3 ships hand tracking enabled by default. The Meta XR Hands Interaction SDK provides HandGrabInteractor (near-range hand grabbing), DistanceHandGrabInteractor (long-range), and HandPoseRecognizer for detecting specific hand configurations. Hands and controllers are automatically switched between based on what the user is holding.

Building a Simple Quest App: VR Sandbox

Build a minimal interactive scene: objects you can grab, throw, and interact with. This covers the essential Quest development loop:

- Set up OVRCameraRig with OVRManager, OVRInput, and two OVRControllerPrefabs - Add OVRInteractionRig for the Meta Interaction SDK on top of the camera rig - Create grabbable objects with Rigidbody and GrabInteractable components - Implement a poke-able button that triggers an event - Add teleportation locomotion using OVRLocomotionController - Build APK via File > Build Settings, sideload via MQDH, test on device ## Passthrough and Mixed Reality on Quest 3

Quest 3's color passthrough cameras enable full mixed reality: digital objects blend with the real environment. This is one of the most compelling features of the Quest 3 hardware.

- Enable Passthrough in Project Settings > Meta XR > Enable Passthrough - Add OVRPassthroughLayer to OVRManager to enable camera feed rendering - Set camera background to transparent for MR blend mode - Use Scene Understanding API to detect floors, walls, and furniture as physics surfaces - Anchor virtual objects to real surfaces using OVRSceneAnchor components ## Optimizing for Quest 3 Hardware

Quest 3 runs Android on Snapdragon XR2 Gen 2 — powerful for a mobile chip, but not a gaming PC. Performance optimization is critical.

- Target 90 FPS (72 Hz minimum) — use the OVR Metrics Tool to monitor - Enable Fixed Foveated Rendering (FFR) Level 2 for significant GPU savings - Keep draw calls under 100 per frame — use GPU instancing and static batching - Texture budgets: 2048x2048 max for most assets, compressed to ASTC on Android - Polygon budgets: 50K–100K total scene tris for comfortable Quest 3 performance - Avoid dynamic shadows where possible — baked lighting is dramatically more performant ## Publishing: App Lab vs. Horizon Store

App Lab (Developer Distribution)

App Lab lets you distribute your app to anyone with a Quest headset via a direct link — no Meta review process required. It's the right starting point for any Quest project: share with testers, distribute to early users, build your audience, and collect feedback before investing in Horizon Store submission.

Meta Horizon Store

The Horizon Store is Meta's main consumer app marketplace. Submission requires completing a content rating questionnaire, providing store listing assets (icon, screenshots, trailer), and passing Meta's technical and content review. Review times vary from 1–4 weeks. 30% revenue share applies to paid apps.

Resources for Meta Quest Developers

• developer.meta.com: Official documentation, SDK downloads, and developer forums
• Meta Quest Developer Hub: Sideloading, logging, and performance tools
• Meta XR Samples (GitHub oculus-samples): Official example projects for every Interaction SDK feature
• Meta Quest Developer YouTube channel: Official tutorials and feature deep dives
• r/oculusdev subreddit: Active community for Quest-specific development questions