Essentials

App compatibility for Meta VR Glasses

Updated: Sep 4, 2026
Three things determine whether an app is compatible with Meta VR Glasses hardware: its architecture, input support, and Store device targeting.
If your app checks the device model to choose features or behavior, review Compatibility mode before testing on Meta VR Glasses.

Architecture: Ship a 64-bit binary

Meta VR Glasses require a 64-bit app binary. A binary that contains only 32-bit native libraries cannot run on this device at all. The same binary still runs on Quest.
In Unity, a 32-bit binary indicates that the project still uses the Mono scripting backend, which targets 32-bit ARM only. For the build you ship, rebuild with the newer IL2CPP backend and ARM64. For iteration, see Optimize Build Iterations and Use Quick Preview, which uses a 32-bit configuration.
If you are bringing an existing Android phone app across, follow Make your existing app compatible with Meta VR devices, which covers the manifest, dependency, and permission changes Horizon OS needs.

Input support: Controllers and hands

Meta Quest Touch Plus controllers are optional for the device and are not included with it.
A 2D Android app runs with eyes and hands, so no controllers are involved.
An immersive app that requires controllers can still be installed because it stays binary compatible with the Quest line. When a person launches it, the Switch to Controllers dialog blocks entry until controllers are active. The dialog asks the person to pick up their controllers and select Continue. Controllers are a separately available accessory, so do not assume the person has a pair.
To make a controller-required immersive app usable without controllers, implement eye and hand input. Do not treat binary compatibility as proof that every interaction works without controllers.
An immersive app that uses hand-tracking APIs declares hand-tracking support and permission in its merged Android manifest. Choose the declaration instructions that match how the app was built:
The manifest states which input the app supports:
  • Omitting both entries means controllers only.
  • Declaring oculus.software.handtracking with required="false", plus com.oculus.permission.HAND_TRACKING, means controllers and hands.
  • Declaring oculus.software.handtracking with required="true" means hands only.
The declaration signals what the app supports. It does not add hand interactions. Declaring hands on an app that cannot be driven by hands produces a broken experience. Do not ship the declaration before the hand-input path works.
Avoid presenting an app’s controller and hand support as Store categories. Store labels and visibility rules can differ from the app behavior that you test.

Input support: Eye and hand input

Choose the implementation instructions that match how the app was built:

Store device targeting

Meta VR Glasses use the same Store delivery system as Quest. For shared account and app-service configuration, see Platform services on Meta VR Glasses.
In the Developer Dashboard, Future devices is an option under Supported Devices. After testing and uploading a build that’s ready for Meta VR Glasses, select Future devices as well as each current Quest device that should receive the build. This marks the build as forward-compatible with Meta VR Glasses and other future devices.
After Meta VR Glasses hardware is released, an existing approved build in the Production release channel can be delivered to Meta VR Glasses devices if it targets Future devices and is otherwise compatible. This does not require a new APK or changes to the build’s device targets.
Be aware that Store labels and visibility rules don’t guarantee runtime input support. You must test the app’s controller and hand behavior to ensure proper behavior on Meta VR Glasses.
com.meta.store.defaultDeviceTargets is an optional Android manifest setting that preselects a build’s Supported Devices when you upload the APK. Use it only when you deliberately want to restrict a build to specific devices or maintain separate builds for different device groups.
Nav Logo
English (US)
© 2026 Meta