Device targeting separates APKs for different Quest generations and capabilities. Understand release performance, size, rollback and governance.
Direct answer
Meta Horizon Store device targeting allows you to maintain different builds of an app for groups of Quest devices. A team can deliver specific assets and features to Quest 3, preserve a backward compatible build, and set targets via the dashboard, AndroidManifest, or upload tool. Flexibility reduces weight and performance compromises, but increases testing matrix, version management, and the risk of involuntary rollback when a target is removed.
A single APK is not always the least risk
Unique features and heavy assets can inflate everyone's package. Segmented builds allow you to adapt content and budget to the capabilities of each group.
Segmentation does not replace runtime detection
A targeted build can still run on models with different states and configurations. Optional resources must be consulted and fallback.
History can trigger rollback
When removing a device from the current build, the store can select the next supported build in the history. The team must validate which version will become active before the change.
CI needs to treat targets as critical configuration
Manifest, CLI and panel can define targets, with precedence rules. Automatic review and build inventory prevent publishing to the wrong group.
Nexus Reading
Separation is valid when it reduces weight or frees up relevant capacity. The additional cost of testing, support and maintenance must be included in the calculation before multiplying tracks.
FAQ
Can I have an exclusive build for Quest 3?
Yes. The documentation allows you to target builds to specific devices or groups, respecting the store's rules.
Does removing a device take the app down?
Not necessarily. The system can roll back to another compatible build; Ending support requires the appropriate commit and lock flow.
Is it worth creating a build for each headset?
Only when the difference in features, size or performance outweighs the cost of testing and maintaining the additional array.
Essential guides to delve deeper into the decision
This editorial analysis was produced by Nexus from the official sources below, consulted on September 18, 2026. The text is original and interprets practical implications for companies.
- Meta Horizon OS Developers — Target app builds by device: segmentation flows, configuration, rollback, purchase blocking, requirements and restrictions.
- Meta Horizon OS Developers — Compatibility mode: automatic compatibility behavior and relationship with the declaration of supported devices.
Date reported by main source: documentation updated on September 4, 2026.