Meta has recently reorganized the structure of its Reality Labs division, separating Horizon OS from the original “Metaverse” business group and elevating it to an independent top-level group. For context, prior to this restructuring, the two main departments under Reality Labs were “Metaverse” and “Wearables”. The former was responsible for the Quest series of headsets, the Horizon OS used in these headsets, and metaverse applications (such as Horizon Worlds), while the latter focused on Ray-Ban/Oakley smart glasses, the development of true AR glasses, and cutting-edge wearable technologies like the Meta Neural Band. Currently, Horizon OS has been moved out of the “Metaverse” department and established as an independent top-level group, led by Ryan Cairns. This department will continue to focus on the development of VR hardware and system platforms. At the same time, Vishal Shah, the former head of the “Metaverse” business group, has been transferred to Meta Superintelligence Labs, where he will be responsible for promoting the integration of Personal Superintelligence between Meta’s platforms and the Reality Labs ecosystem. Gabriel Aul has taken over as the new head, and the “Metaverse” department will continue to focus on developing metaverse application products such as Horizon Worlds in the future.

IT Home has noticed that Andrew Bosworth, Meta’s Chief Technology Officer, emphasized in an internal memo sent to Reality Labs that this organizational restructuring does not mean a reduction in the priority of Meta’s “metaverse projects”: “The focus of our metaverse work remains unchanged; it is still a core company-wide strategy. We have proven to the industry that our direction is correct, and competitors are trying to catch up, so we must continue to maintain our advantage.” Bosworth also pointed out that as Meta deepens its capabilities in the fields of AI and general compute, VR is transforming from a pure gaming platform into a broader platform covering entertainment, productivity, and social interaction. External analysts believe that the independence of Horizon OS from the “Metaverse” group may be intended to strengthen the independence of the operating system ecosystem, allowing it to directly compete with Google’s newly launched Android XR system in the future. The latter has already made its debut on Samsung’s Galaxy XR headset and plans to be rolled out to more brand devices next year.

Operate against explicit service contracts

Quality, latency, cost and failure behavior should be defined before optimization begins. This keeps local improvements from degrading the user-visible system. Version configuration and state.

Prompts, model routes, caches and data dependencies can change behavior without application code changes. Versioning makes regressions reproducible and rollback practical.

Prefer graceful degradation

When a dependency fails or capacity tightens, reduce optional work or use a clear fallback instead of allowing latency and errors to cascade through the full request path. Operate against explicit service contracts.

Quality, latency, cost and failure behavior should be defined before optimization begins. This keeps local improvements from degrading the user-visible system.

Version configuration and state

Prompts, model routes, caches and data dependencies can change behavior without application code changes. Versioning makes regressions reproducible and rollback practical. Prefer graceful degradation.

When a dependency fails or capacity tightens, reduce optional work or use a clear fallback instead of allowing latency and errors to cascade through the full request path.

Operate against explicit service contracts

Quality, latency, cost and failure behavior should be defined before optimization begins. This keeps local improvements from degrading the user-visible system. Version configuration and state.

Prompts, model routes, caches and data dependencies can change behavior without application code changes. Versioning makes regressions reproducible and rollback practical.

Prefer graceful degradation

When a dependency fails or capacity tightens, reduce optional work or use a clear fallback instead of allowing latency and errors to cascade through the full request path. How to read the development beyond the headline.

The reported development is most useful when separated into confirmed facts, forecasts and interpretation. Product timelines, pricing, supply constraints, regulation and customer adoption can all determine whether an early headline becomes a durable shift. Readers should update the thesis as concrete follow-through appears instead of treating an initial announcement or market reaction as the final outcome.

What to watch next

Useful signals include shipped products, independently observed performance, customer commitments, pricing changes, financial guidance and regulatory decisions. Those indicators show whether the development is changing real operations rather than only sentiment.