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.
Look for continuity without constant callbacks
A companion should use remembered context when it helps, not repeatedly announce that it remembers. Good continuity reduces the need for the user to restate important information and makes recurring activities easier to resume. If every response references old history, personalization can feel forced rather than natural.
Check how the system handles a mistake
Correct a fact, reject a suggestion or change topic abruptly. The companion should repair the interaction and update the relevant state instead of arguing or repeating the same assumption later.
Evaluate whether the relationship remains user-led
Notifications, progression and premium features should support the user’s chosen interaction rather than manufacture urgency. Quiet hours, frequency controls and easy cancellation are practical signs that the product respects the user’s pace.
Compare richer media with the core conversation
Voice, images and video are valuable when they reinforce the same identity. If media quality is inconsistent or arrives too slowly, a simpler response may produce a better overall experience.
Test the product over more than one session
A first conversation can show personality, but long-term quality appears only after the system has accumulated memory, preferences and notifications. Return later, change a preference and see whether the companion adapts without losing its core identity. Longitudinal testing also exposes repetition and stale context that a short demo cannot reveal.
Use controls as part of the quality test
Try the memory, notification, privacy and reset controls before you need them. A strong companion should make important settings understandable without forcing the user to delete the entire relationship to repair one problem. The best experience becomes more relevant over time while remaining easy to correct.
A final long-term check
Repeat the same test after several days and after changing one setting. AI products accumulate memory, synchronization state and billing or permission history, so problems may appear only after the first-session novelty has passed. The strongest products remain understandable as history grows: users can see what changed, correct the relevant state and continue without rebuilding the entire relationship.