Bringing React Native to Meta Quest: Getting Started with VR Development
At React Conf 2025, Meta announced official React Native support for Meta Quest headsets, marking a major milestone in the framework's expansion beyond mobile. This opens the door for developers to build virtual reality (VR) apps using familiar tools and patterns, leveraging the existing React Native ecosystem. Below, we answer common questions about this new capability, from technical foundations to practical setup steps.
What is the new React Native support for Meta Quest?
React Native now officially supports Meta Quest devices, allowing developers to build and ship VR applications using the same codebase and workflow as mobile apps. Announced at React Conf 2025, this integration builds on the Many Platform Vision, which aims to extend React Native to diverse form factors without fragmenting the ecosystem. The support means that Android-based Meta Horizon OS on Quest headsets can run React Native apps with minimal changes. Developers can use Expo Go for rapid prototyping or create development builds for native features. This is a significant step in making VR development more accessible to the wide community of React Native developers.
How does React Native work on Meta Quest given its Android-based OS?
Meta Quest devices run on Meta Horizon OS, which is derived from Android. This compatibility means that all existing Android tooling, build systems, and debugging workflows—like ADB, Gradle, and the React Native Metro bundler—work without modification. Android libraries and APIs remain accessible, and platform-specific capabilities (e.g., hand tracking, 3D rendering) can be integrated through React Native's native modules layer. The React Native team has not introduced a new runtime; instead, they leveraged the existing Android port. Developers already building for Android can reuse much of their code and configuration, simply adding VR-specific UI and interactions on top.
How can developers get started with React Native on Meta Quest?
Getting started is straightforward, especially for those familiar with Expo. First, install Expo Go from the Meta Horizon Store on the headset. Then create a standard Expo project (no special template needed): npx create-expo-app@latest my-quest-app. Start the development server with npx expo start. On the Quest headset, open Expo Go and scan the QR code displayed by the CLI. The app launches in a new window, and you can iterate with live reloading just like on mobile. This workflow supports rapid prototyping without complex setup. For native features not available in Expo Go, developers can later switch to development builds using Expo's expo-dev-client or a bare React Native project.
What is the step-by-step process to run an Expo app on Meta Quest?
- Install Expo Go on the headset — Find it in the Meta Horizon Store and install directly on your Quest device.
- Create or use an Expo project — Run
npx create-expo-app@latest my-quest-appto create a new project, or navigate to an existing one. - Start the dev server — Use
npx expo startto launch the Metro bundler. - Connect with Quest using Expo Go — Open Expo Go on the headset, select "Scan QR code," and point the headset camera at the terminal's QR code.
- Iterate as usual — Code changes are reflected immediately on the device through hot reloading, just like on Android or iOS.
What about development builds and native features?
Expo Go is excellent for early-stage development, but once you need native modules—like hand tracking, spatial audio, or custom VR interactions—you'll need a development build. Expo's expo-dev-client lets you create a custom version of Expo Go that includes any native dependencies you add. Alternatively, you can eject to a bare React Native project managed by Android Studio. The process mirrors adding native features on mobile: install a plugin (e.g., expo-vr or a community package), rebuild the app, and deploy to the Quest. The key is that the Android foundation remains unchanged, so existing tooling like Gradle and Android Studio extensions works seamlessly.
Are there platform-specific considerations for VR design?
Yes, designing for VR introduces new UX patterns compared to mobile. React Native on Quest supports standard components, but you'll need to consider spatial UI—placing elements in 3D space, handling gaze or controller input, and ensuring comfortable viewing distances (around 1–2 meters). Use large, readable text (avoid small fonts) and avoid rapid motion that could cause disorientation. React Native's existing flexbox layout still applies to 2D overlays, but you may also use Three.js or react-three-fiber for immersive 3D scenes. The Meta XR SDK provides native modules for hand tracking and spatial anchors, which can be accessed via React Native's bridge. Start with a 2D interface in a floating window, then gradually add 3D layers as you experiment.