Features can implicitly elevate the minimum system and exclude old devices. See how to detect API, target builds, and plan updates.

Direct answer

Meta documents that an application can require a minimum version of Horizon OS explicitly, via the `uses-metavr-sdk` element, or implicitly, when using a newer device, permission, or API. Camera2 with direct access to frames, for example, raises the minimum to v74. When multiple dependencies combine, the higher requirement prevails and Horizon Store stops showing or updating the app on incompatible devices.

Indirect dependence also changes the minimum

Camera permission, headset model, or platform API can increase the requirement without obvious change to the manifest. The build panel must be reviewed with each release.

Visible version is not API level

Meta recommends consulting your own compatibility APIs at runtime, without inferring version from internal package metadata.

Raising the floor reduces the installed base

Incompatible users will not install or receive the update. The decision needs to compare the benefit of the resource with scope, support and contractual obligation.

Segmented build can preserve operation

When the store and product allow, variants by device or capacity avoid imposing the highest demand on the entire fleet.

Nexus Reading

Maintain a critical device, firmware, API, and function matrix; any elevation of the minimum requires upgrade testing, communication, and path forwarding for legacy users.

FAQ

How to declare the minimum?

Use the `uses-metavr-sdk` element in the manifest with the desired version, according to the Meta documentation.

What happens to old appliances?

The store does not display or update to incompatible versions.

Can I trust the displayed version name?

Not for technical compatibility. Refer to the API level by the official functions indicated by Meta.

Essential guides to delve deeper into the decision

Primary sources and references

This editorial analysis was produced by Nexus from the official sources below, consulted on October 26, 2026. The text is original and interprets practical implications for companies.

Date reported by main source: documentation updated on October 14, 2026; analysis published on October 26, 2026.