Meta Horizon OS Quick Start Guide

Meta Horizon OS

Quick Start Guide

Build, test, deploy, and prepare your first app for Meta VR devices.

Updated

September 9, 2026

Audience

Developers building for Meta VR devices

Scope

Horizon OS, development setup, deployment, testing, and Store preparation

A practical reference from platform orientation through first on-device deployment and Store preparation.

Meta Horizon OS Quick Start Guide

At a glance

Horizon OS is Meta’s operating system for Meta VR devices. It is built on the Android Open Source Project

(AOSP), allowing Android apps to run natively while supporting immersive VR and mixed reality development.

This guide covers platform fundamentals, developer setup, development-path selection, first deployment, testing,

and preparation for publishing.

1. What is Horizon OS?

Horizon OS supports game engines, native C/C++ through OpenXR, web-based experiences through WebXR, and

Kotlin-first spatial applications through Meta Spatial SDK.

Feature

Standard Android

Horizon OS

Display

Flat screen

Stereoscopic VR / passthrough MR

Input

Touch screen

Controllers, hand tracking, gaze, voice

App rendering

2D window

2D panel in 3D space, or fully immersive

App distribution

Google Play

Meta Horizon Store

Apps render as flat panels floating in space by default. Mobile gestures such as tap, swipe, and scroll map to

controller or hand input. Developers can optionally use immersive 3D environments, spatial audio, passthrough,

and mixed reality capabilities.

Dependency note:

Google Mobile Services such as Firebase, Google Auth, and Google Play Billing are not

available on Horizon OS. Applications depending on these services need alternatives.

Hardware considerations

• Meta Quest headsets are standalone, wireless VR/MR devices; a PC is not required for normal use.

• Quest 3 and Quest 3S are current-generation headsets in the reference guide.

• PSS kill limits are 4.4 GiB for Quest 2 and Quest Pro, and 5.75 GiB for Quest 3 and Quest 3S. Target comfortably

below these limits.

• The GPU is a mobile GPU. Optimize with a high-end phone rather than a desktop GPU as the performance

mental model.

• Supported refresh rates include 72 Hz, 90 Hz, and 120 Hz depending on device and application settings.

Dropped frames can affect comfort.

• Touch Plus controllers ship with Quest 3/3S, and all headsets support controller-free hand tracking.

• Quest 3/3S support AV1 decode; use HEVC as a fallback for Quest 2.

2. Set up your developer environment

Before installing your own applications on a Meta VR device, create a developer account and enable developer

mode. Developer mode permits apps to be installed directly from a computer rather than only from the Meta

Horizon Store.

1. Create a developer account

dashboard, documentation, and app submission workflow.

2. Install the Meta Horizon mobile app

Meta Horizon OS Quick Start Guide

Install the Meta Horizon app on iOS or Android and pair your VR device through the app.

3. Enable developer mode

In the mobile app, open Devices, select your device, open Developer Mode, and turn it on. A Meta developer

account is required first.

4. Connect your device

Use a USB-C data cable to communicate between your computer and headset. A charge-only cable will not work

for development.

On-device debugging:

Put on the headset and accept the USB debugging prompt when it appears. Meta's

current setup documentation also notes that Windows developers may need Oculus ADB Drivers when pushing

builds from Windows.

3. Developer tools

Meta Quest Developer Hub

Meta Quest Developer Hub (MQDH) is the recommended desktop tool for device management, app deployment,

log viewing, screen casting, and performance analysis. It can also support AI-assisted development workflows.

Simulation

Meta XR Simulator provides an OpenXR runtime for testing supported XR applications on a development computer

without a headset. It models supported device profiles and inputs but does not emulate the complete Android

operating system or physical headset hardware.

For 2D Android applications, Meta Spatial Simulator can run the app as a panel on the desktop. Physical-device

testing remains important because simulators do not reproduce every device-specific or spatial behavior.

4. Choose your development path

Choose a path based on your existing skills, whether you are porting an existing application or building something

new, and how immersive the experience needs to be.

Starting point

Recommended direction

I have a mobile app

Bring an Android or iOS app to Meta VR as a 2D panel. Android applications can be shipped

with minimal changes; Meta Spatial SDK can add spatial features such as 3D panels, spatial

anchors, and environment blending.

I have a web app

Use web technologies and WebXR where the experience and target browser capabilities fit

the project.

Building something new

Choose Android / Spatial SDK, Unity, Unreal, Native OpenXR, or Web according to the

experience and team skill set.

Not sure yet

Start with the development path closest to your existing skills, prototype with simulation, and

validate on physical hardware.

Minimum system requirements

Path

IDE / tool

Minimum

Android / Spatial SDK

Windows / macOS / Linux

Android Studio Narwhal (2025.1.1)+

8 GB RAM

Unity

Windows / macOS

Unity 2022.3 LTS+

16 GB RAM, dedicated

GPU

Unreal

Windows

Unreal Engine 5.3+ (Meta fork recommended)

32 GB RAM, NVIDIA

GPU

Meta Horizon OS Quick Start Guide

Path

IDE / tool

Minimum

Web

Any

Any code editor + Chrome

Minimal

Native

Windows

Visual Studio 2022 + CMake

16 GB RAM

5. Deploy your first app

Regardless of the development path, the first device deployment follows a common pattern:

• Build your APK from Android Studio, Unity, Unreal, or the command line.

• Connect the headset with a USB-C data cable.

• Put on the headset and accept the “Allow USB Debugging” prompt.

• Install the APK with ADB.

adb install path/to/your.apk

After installation, find the app on the device under

Library > Unknown Sources

If the device is not detected

• Run

adb devices

and verify that the headset appears.

• Check that the USB-C cable supports data rather than charging only.

• Confirm developer mode is enabled.

• Put on the headset and accept USB debugging on the device.

• On Windows, confirm the required ADB drivers are installed.

The USB debugging approval happens on the headset. If

adb devices

does not show the device, work through the

cable, driver, developer-mode, and debugging-approval checks before troubleshooting the application itself.

Build with Store submission in mind

Plan for Store requirements from the beginning. Meta Horizon Store apps must meet applicable Virtual Reality

Checks (VRCs), which cover areas such as performance, functionality, input, assets, security, and accessibility.

Reviewing these requirements early can reduce rework before submission.

6. After your first build

Test across devices

Verify the application on Quest 3, Quest 3S, and any older headsets you intend to support.

Meet technical requirements

Review the VRC requirements applicable to your app type and distribution path.

Complete Data Use Checkup

Declare how your application uses data as required for submission.

Set up your organization

Verify your developer organization in the Developer Dashboard.

Create the app in the dashboard

Create an app page before uploading a build. The dashboard generates the app ID used for the app.

Meta Horizon OS Quick Start Guide

Submit for review

Upload your build, complete Store metadata and assets, and submit for review. Meta checks the submission

against applicable VRCs and policies.

Launch

Once approved, publish using the pricing model appropriate for your application.

7. Practical pre-submission checklist

Developer account is active and required verification is complete.

Target Quest devices have been identified and tested.

Developer mode and USB debugging work on the test device.

Build installs and launches reliably.

Performance has been checked on real hardware.

Input works with the interaction methods supported by the target experience.

Required VRCs have been reviewed and addressed.

Data Use Checkup is complete where required.

Store metadata, screenshots, and other required assets are ready.

Release and beta-testing plans are defined.

8. Quick reference

Development flow

Choose path

→

Set up account and device

→

Install tools

→

Prototype or simulate

→

Build

→

Deploy

→

Test on

hardware

→

Check VRCs and submission requirements

→

Submit

→

Review

→

Launch

Core deployment command

adb install path/to/your.apk

Key principle:

Use simulation for fast iteration, then validate important behavior and performance on the physical

target device before release.

Document note

This guide is organized as a practical quick-start reference. Platform capabilities, device support, development

tools, requirements, and Store policies can change; consult the current Meta Horizon OS developer documentation

when implementing or submitting a production application.

Meta Horizon OS Quick Start Guide

Prompt to Clone This Meta Horizon OS Quick Start Guide

Apply this example's core structure, strategic pacing, and structural hierarchy directly to your own topic.

What are you generating today?