Compose and React Native gain anchoring, priority and fallback without migrating the entire app to a 3D engine. See when the pattern makes sense.

Direct answer

On September 24, 2026, Meta released version 1.0.0 of the VR Layout SDK to create spatial windows around the main panel of an Android application. The app remains non-immersive and maintains its Activity architecture and interface in Jetpack Compose or React Native. The SDK provides anchoring, size, priority, and fallback strategies; Versions prior to Horizon OS 207 display compatible content without spatial positioning. It is a useful bridge for productivity, but it does not replace a 3D system when there are volumetric objects or manipulation of the environment.

2D application gains space without total rewrite

Tools, details, and controls can occupy separate panels while the core continues to use familiar Android components.

Priority treats limited capacity

Not every declared window will be positioned. Order and preemption need to reflect task importance, not just visual convenience.

Fallback preserves continuity

Inline keeps the content within the panel and Drop omits it when there is no space. The choice must ensure that essential actions never disappear.

Too much space increases cognitive cost

Separating panels can improve comparison, but also spread attention. Distance, hierarchy and persistence need to follow the actual task.

Nexus Reading

Start with a high-value function, such as a side tool or reference, and compare time, error, and understanding against the 2D version before expanding the layout.

FAQ

Is it necessary to migrate to a 3D engine?

No. The SDK is designed for existing Android apps in Compose or React Native.

What happens before Horizon OS 207?

The library uses fallback behavior instead of creating spatial windows.

When to use the Spatial SDK?

When the experience requires 3D objects, spatial entities or deeper manipulation of the environment.

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 September 26, 2026. The text is original and interprets practical implications for companies.

Date reported by the main source: September 24, 2026.