Oculus Developer Mode: What You Can Actually Do With It

Just completed the setup? This post picks up where our Oculus Developer Mode Set Up Guide leaves off and Developer Mode is active. Here are some benefits:

Oculus Developer Mode on the Quest transforms the headset from a consumer device into a fully programmable development platform. The consumer experience is deliberately walled: apps come from the Meta store, settings are locked down, and there is no direct access to the underlying Android system. Developer mode lifts those restrictions entirely.

With it active you can deploy your own builds directly to the headset, communicate with it over ADB, profile performance in real time, and iterate on your project without touching the store or waiting on review cycles. If you are building VR experiences, whether for games, training, medical applications, entertainment, or anything else, this is the mode you will live in throughout development.

Here is a practical breakdown of what you can now do and how to make the most of it.

1. Sideload Your Own Builds Directly to the Headset

Sideloading is the core capability developer mode unlocks. It lets you install an APK directly onto the headset from your development machine, bypassing the Meta store entirely. For VR developers, this means you can build in Unity or Unreal, export an APK, push it to the headset, and be testing on device within minutes.

Via ADB (Android Debug Bridge)

ADB is the command-line tool that communicates between your PC and the headset. With developer mode active and the headset connected via USB-C, the basic install command is:
adb install path/to/your-app.apk

Once installed, sideloaded apps appear in your Quest library under Unknown Sources. You can launch, uninstall, and update them exactly as you would any store app.

Via Meta Quest Developer Hub (MQDH)

If you prefer a GUI over the command line, Meta’s own developer hub handles APK deployment via drag and drop. It also gives you a device manager view, real-time performance metrics, and log output in one place. Download it from the Meta developer portal and log in with your developer account.

Via SideQuest

SideQuest is a popular third-party tool that simplifies sideloading considerably. It handles the ADB layer for you, provides a clean interface for managing installed apps, and includes a catalogue of community content that can be useful for testing and reference. Connect via USB initially, then switch to wireless ADB for cable-free iteration.

WIRELESS ADB

Once connected via USB, run ‘adb tcpip 5555’ then ‘adb connect [headset-ip]:5555’ to switch to wireless debugging. You can then iterate and deploy builds without being tethered. Check the headset IP in Settings > Wi-Fi > your network.

2. Build and Test in Unity or Unreal Without Store Approval

The store review process exists for consumer distribution. During development it would be a significant bottleneck. Developer mode removes it entirely, giving you a fast, direct path from engine to headset.

Unity workflow

In Unity, set your build target to Android and configure the XR settings to target the Quest platform via the Meta XR SDK (formerly the Oculus Integration package). To deploy directly to the headset:
Go to Build Settings and check Development Build and Script Debugging if you want to attach the Visual Studio debugger
Select Build and Run to have Unity build the APK and push it to a connected headset automatically
Use Oculus Link as a faster prototyping loop: your PC renders and streams to the headset over USB, cutting out the Android build step during early iteration

Oculus Link is particularly useful in the early stages of a project when you are iterating quickly on mechanics and interactions. Switch to proper on-device builds once you need to test performance accurately or access Quest-native features like hand tracking.

Unreal Engine workflow

In Unreal, the OculusVR plugin handles Quest deployment. Set your project to package for Android (ASTC texture compression), connect your headset, and use Launch from the toolbar to build and deploy directly. As with Unity, you can also use Quest Link for streaming-based iteration during prototyping.

PERFORMANCE BASELINE

The Quest runs on mobile hardware. Even with developer mode active, your scene budget is considerably tighter than PC VR. Target 72fps minimum on Quest 2, 90fps on Quest 3. Use fixed foveated rendering from the outset and test on device regularly — Link hardware-accelerates rendering on your PC and will not surface the real performance constraints until you run a native build.

3. Profile and Debug Performance in Real Time

Developer mode enables a set of performance overlays and debugging tools that are not available in consumer mode. These are essential for building experiences that run smoothly and comfortably on Quest hardware.

In-headset performance overlay

With developer mode active, you can enable a real-time heads-up display inside the headset showing frame rate, CPU and GPU usage, thermal state, and memory consumption. To enable it, go to Settings > Developer in the headset menu and toggle Performance Overlay. This gives you live feedback while running your build without needing an external tool.

Meta Quest Developer Hub performance tab

MQDH surfaces the same metrics on your PC screen in a more readable format, with timeline graphs for frame rate, GPU load, and CPU usage. It is particularly useful when you are trying to identify frame spikes or thermal throttling during longer play sessions.

ADB logcat for runtime logs

ADB logcat streams the device log to your terminal in real time. For catching exceptions, tracking down crashes, and monitoring your application during a session, it is indispensable:
adb logcat -s Unity

Filtering by the Unity tag keeps the output readable. Pipe to a file if you need to review a full session log after the fact.

KEY DEVELOPER MODE DEBUG CAPABILITIES

• Real-time framerate and GPU/CPU overlay inside the headset
• ADB logcat for live application log streaming
• MQDH performance timeline for frame spike analysis
• Visual Studio debugger attachment for live C# debugging in Unity builds
• File transfer via ADB for pushing assets, reading saved data, and pulling screenshots

4. Access Advanced Features Not Available in Consumer Mode

Beyond the core build and test workflow, oculus developer mode surfaces a number of settings and capabilities that are either hidden or disabled in the consumer experience.

Hand tracking and experimental features

Hand tracking on Quest 2 and Quest 3 is enabled via the developer settings menu in the headset. With oculus developer mode active you can also enable experimental hand tracking features before they reach the consumer release, which is useful if you are building interactions that depend on precise finger pose data.

Passthrough and mixed reality development

Quest 3’s colour passthrough gives developers access to mixed reality capabilities: blending your VR content with a live view of the physical environment. Developer mode is required to access the full passthrough API in your builds. This is increasingly relevant for training applications where spatial context in the real environment matters alongside the virtual content.

File system access via ADB

Developer mode gives you read and write access to the headset file system over ADB. This is useful for pushing configuration files or localisation assets to a running app, pulling save data and logs for inspection, and managing content on headsets during a multi-device deployment.
adb pull /sdcard/Android/data/com.yourcompany.yourapp/files/ ./local-backup

Multi-headset testing

For multi-user or networked VR experiences, developer mode lets you manage and deploy to multiple headsets simultaneously via ADB. You can script deployments to push a build to an entire fleet in one command, which becomes important when testing social or collaborative experiences that require multiple devices running concurrently.

TARGETING MULTIPLE DEVICES

When multiple headsets are connected, ADB requires you to specify the target device. Run ‘adb devices’ to list serial numbers, then use ‘adb -s [serial] install yourapp.apk’ to target a specific headset. For fleet deployments, script this with a loop over the device list.

5. What This Makes Possible at Sliced Bread

At Sliced Bread, Oculus developer mode is where all of our Quest-based projects live during production. Whether we are building a VR training simulation for a safety-critical environment, a medical procedure walkthrough, or an immersive onboarding experience, the ability to deploy, test, and iterate directly on device without store involvement is fundamental to how we work.

The experiences that matter most to our clients are bespoke by definition. They mirror specific environments, specific procedures, and specific learning objectives that no off-the-shelf store app will ever address. Sideloading is how those experiences get from the engine onto the headset and into the hands of the people they were built for.

If you are building your first Quest project, or exploring what VR could do for your organisation’s training or communication needs, developer mode is where that exploration begins.

VR DEVELOPMENT  |  OCULUS QUEST  |  DEVELOPER TOOLS

If you have an idea for a vr game or vr training project, you can contact us here, or drop us an email at info@sbanimation.com or give us a call on +44 (0)207 148 0526. 

You can also view our LinkedIn company page here.