Skip to content

How to Build React Native Apps for Meta Quest

updated

The React Native team has published a guide to building apps for Meta Quest, following the announcement of official support for the headsets at React Conf 2025. The post covers how to get started, what works today, and how to ship VR apps with the tools React Native developers already use.

Built on Android

Meta Quest devices run Meta Horizon OS, which is based on Android. As a result, existing Android tooling, build systems, and debugging workflows carry over with minimal changes. Quest support does not introduce a new runtime or development model. It builds on React Native's existing Android foundation, so platform-specific capabilities can be added without fragmenting the framework.

Getting started with Expo Go

Expo Go is available on the Meta Horizon Store and can be installed directly on the headset. No special template is needed:

npx create-expo-app@latest my-quest-app
cd my-quest-app
npx expo start

Scanning the QR code with the headset camera launches the app in a new window, with live reloading and the same edit-refresh cycle used on Android and iOS. Expo Go is meant for early development and UI work. When native modules or deeper platform integration are needed, standard Expo development builds run directly on the Quest.

Project configuration

Quest apps need platform-specific Android configuration, product flavors, and application metadata to run correctly and qualify for store submission. The expo-horizon-core config plugin applies these requirements at build time. It accepts options such as horizonAppId, defaultHeight, defaultWidth, supportedDevices (for example quest2|quest3|quest3s), disableVrHeadtracking, and allowBackup. The post also recommends setting "orientation": "default" and adding build-variant scripts, for example:

"quest": "expo run:android --variant questDebug"

Projects that do not use Expo can apply the same changes by hand. These include a Quest build flavor in android/app/build.gradle, setting the horizonAppId, defining a default panel size in the manifest, declaring supported devices, removing prohibited permissions, adjusting the minimum Android SDK, and adding runtime checks. The plugin's implementation serves as a reference for these steps.

Platform differences

Meta Horizon OS is built on AOSP, so Google Mobile Services such as Play Services are unavailable. Features like SMS and GPS, along with restricted permissions, are either unavailable or prohibited. Most libraries work as long as they rely only on standard React Native and Android APIs. Libraries that assume touch-only input, mobile-only hardware, or Google services need adaptation. Expo provides drop-in replacements for location and notifications.

For shared codebases, expo-horizon-core exposes ExpoHorizon.isHorizonDevice, ExpoHorizon.isHorizonBuild, and ExpoHorizon.horizonAppId so apps can guard platform-specific behavior.

Designing for VR

VR interfaces are viewed at a distance and controlled with controllers, hand tracking, or a mouse and keyboard. The post recommends larger hit targets, more spacing, readable typography, clear focus states, and hover- and focus-based navigation instead of touch-only assumptions. Responsive layouts that adapt to resizable windows apply here, much as they do on desktop, tablet, and foldable devices.

Why it matters

For teams already shipping React Native on Android, targeting Quest mostly means adding configuration and handling the platform differences above, rather than adopting a new stack. The post links to a reference project, Callstack's showcase app from React Conf, and additional articles, an ebook, a podcast, and a live stream.

Source: reactnative.dev