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.

How to interpret the development beyond the headline

Fast-moving technology and crypto stories should separate confirmed facts from forecasts, market reaction and interpretation. Product launch, adoption, liquidity, regulation and execution can all determine whether an early headline becomes a durable shift. The useful follow-up is concrete evidence: shipped capability, user growth, audited transactions, financial guidance or regulatory decisions that confirm or weaken the initial narrative.

Watch second-order effects

Major developments can change incentives for developers, creators, exchanges, infrastructure providers and users. The practical impact may appear through costs, standards, distribution or policy rather than through the headline event itself. Keeping long-term scenarios conditional makes later updates easier to interpret without rewriting early speculation as fact.

Separate market sentiment from product execution

Price movement and social attention can react instantly, while technology deployment takes longer. A useful analysis asks what operational milestone would prove that the story has changed real behavior. That milestone might be production use, a measurable cost change, a regulatory approval or sustained customer demand rather than one day of market volatility.

Identify the assumptions behind the forecast

Every long-term scenario depends on assumptions about adoption, competition, capacity and policy. Making those assumptions explicit helps readers understand what evidence would cause the outlook to improve or weaken.

Practical implementation check

Before adopting the mechanism described above, define the exact business rule, who controls it and what evidence will show that it worked. Test the failure path as carefully as the successful path, especially when rights, payments or wallet actions are involved. The final system should also document versioning, rollback and the assumptions that may become stale over time. That turns a one-off experiment into an operating model that creators, users and developers can understand.