Building VR Apps with React Native on Meta Quest: A Comprehensive Guide

Overview

React Native has long been the bridge between cross-platform development and native performance, starting with Android and iOS and expanding to Apple TV, Windows, macOS, and the web via react-strict-dom. In 2021, the Many Platform Vision outlined a future where React Native could adapt to new devices without fragmenting the ecosystem. At React Conf 2025, that vision took a significant leap forward with official React Native support for Meta Quest devices. This guide walks you through everything you need to know: from getting started with a basic Expo app on your headset, to leveraging development builds and native features, to avoiding common pitfalls. By the end, you'll have a solid foundation for building and shipping VR applications using familiar tools and patterns.

Building VR Apps with React Native on Meta Quest: A Comprehensive Guide

Meta Quest devices run Meta Horizon OS, an Android-based operating system. This means your existing Android tooling, build systems, and debugging workflows transfer almost seamlessly. If you've built React Native apps for Android before, you're already most of the way there. The key differences lie in the spatial interface, input methods (controllers, hand tracking), and performance considerations unique to VR.

Prerequisites

Before diving in, make sure you have the following:

A Meta Quest 2, 3, or Pro device with the latest Meta Horizon OS update.
Node.js (v18 or newer) and npm or yarn installed.
Expo CLI or the React Native CLI set up on your development machine.
Basic familiarity with React Native and command-line tools.
Optional but recommended: a Meta Developer Account for deploying to the store.

Step-by-Step Instructions

Setting Up Your Environment

Because Meta Horizon OS is based on Android, you can use the same development environment as for any Android React Native app. Ensure you have:

Android Studio (or at least the Android SDK and platform tools) installed.
USB debugging enabled on your Quest device (enable developer mode first via the Meta Horizon mobile app).

For the fastest iteration, Expo Go is the recommended starting point. It eliminates the need for a full native build during early development.

Running an Expo App on Meta Quest

Follow these steps to launch your first React Native app on your Quest headset using Expo Go:

Install Expo Go on the headset
Open the Meta Horizon Store on your Quest, search for “Expo Go,” and install it. This app acts as a runtime for your development builds.
Create a new Expo project
Run the following in your terminal:
```
npx create-expo-app@latest my-quest-app
cd my-quest-app
```
Start the development server
```
npx expo start
```
This will launch the Expo CLI, which shows a QR code in the terminal.
Connect your headset
Put on your Quest, open Expo Go, and use the headset’s camera to scan the QR code. The app will open in a new window on the device. You’ll see live reloading — any changes you save on your machine update instantly on the headset.
Iterate as usual
Edit App.js or your components and watch the changes appear in real time. The workflow is identical to developing for Android or iOS with Expo.

This method works best for prototyping and UI experimentation. However, to access native VR features like controllers or hand tracking, you’ll need to move to a development build.

Moving to Development Builds

Development builds allow you to include native modules and custom platform code. Here’s how to transition from Expo Go:

Create an Expo development build
Run:
```
npx expo run:android
```
This compiles a native Android app with your Expo project and code. You’ll need Android Studio properly configured.
Install the build on your headset
Connect your Quest via USB, and the build process will automatically deploy the APK. Alternatively, you can sideload using adb install.
Test with native features
Once installed, you can use libraries like react-native-quest (community) or react-native-vr to access spatial anchors, controllers, and more. For example:
```
import { VrController } from 'react-native-quest';

function handleButtonPress(event) {
  console.log('Controller button pressed:', event.nativeEvent.button);
}
```

Accessing Native Features

Meta Quest’s native capabilities include hand tracking, controller input, passthrough AR, and spatial anchors. While not all are exposed via React Native’s core, community packages are emerging. For production apps, you may need to write native Java/Kotlin modules or use expo-modules-core to bridge APIs. The official React Native for Meta Quest support ensures that standard Android APIs (like android.hardware) work out of the box.

Common Mistakes

Assuming it’s just like mobile
VR has unique UX constraints: motion sickness, field of view, and depth perception. Test extensively on the headset.
Skipping Expo Go for initial prototyping
Expo Go saves hours of build time. Don’t jump straight to development builds until you need native features.
Forgetting to enable Developer Mode
Without it, your headset won’t accept side-loaded apps or USB debugging. Activate it via the Oculus mobile app.
Ignoring performance optimization
VR requires 72+ FPS. Profile your app using React DevTools and the Unity/Unreal profiler (if you bridge). Avoid unnecessary re-renders.
Not handling input properly
Touch gestures don’t translate directly to VR. Use onPointerEnter / onPointerLeave events or integrate controller libraries.

Summary

React Native on Meta Quest brings the power of cross-platform development to virtual reality. By building on Android foundations, it offers a smooth transition for existing React Native developers. Start with Expo Go for rapid prototyping, then migrate to development builds for native VR features. Keep performance and UX top of mind, and you can ship immersive apps using the same tools you already love.

Tags: