Meta Horizon OS

Original Article ↗ Hacker News Discussion ↗

Meta is rebadging its Quest software stack as “Meta Horizon OS” and licensing it to hardware makers like ASUS, Lenovo and Xbox, positioning it as an Android-style platform play for VR/AR headsets. Commenters are split on whether this is genuine openness or “open-washing,” noting that Meta will still control the core OS, app store and data collection while competitors like Google and Apple push their own closed ecosystems. The thread also questions the long‑term viability and use cases of consumer VR, highlights developer‑experience gaps versus Apple’s visionOS, and raises strong privacy concerns about adopting an operating system from an ad‑driven company.

What Meta Horizon OS Is (and Isn’t)

  • Built on Android/AOSP and the existing Quest stack; not a new kernel.
  • “Open” mainly means: other OEMs (ASUS, Lenovo, Xbox/ Microsoft, etc.) can ship headsets running Horizon OS and access the Meta store and ecosystem.
  • Not open source, not sideload-free; likely requires business agreements. Several commenters see it as “Android-style” openness, not PC-style.

App Stores, “Openness,” and Google/Steam

  • Meta explicitly invites Google Play as a 2D app store on Horizon OS “with the same economic model.”
  • Many infer native 3D/VR app stores (e.g., Google selling Horizon-native VR apps) are not welcome; this is seen as preserving Meta’s walled garden.
  • Steam is mentioned mainly in the context of streaming (Steam Link), not as a native store.
  • Some think this is positioning for future antitrust defenses: Meta can say it invited Google, who refused.

Business Strategy & Comparisons

  • Widely framed as “Meta wants to be Android of XR”: commoditize hardware, own OS + store + data.
  • Others compare to Apple’s early Mac clone program or Microsoft’s abandoned Windows Mixed Reality.
  • Skepticism: why would OEMs compete with Meta’s subsidized Quest hardware if Meta still owns the store and user relationship?

Developer Experience & Ecosystem

  • Quest dev today is mostly Unity/Unreal, with native OpenXR and some web options; there’s frustration about lack of a cohesive, high-level “visionOS/SwiftUI-like” framework for productivity apps.
  • Leaked hints of a JS-based “spatial” SDK using Meta’s Spark tools; some welcome low-bar JS, others complain about JS everywhere.
  • App Lab’s promotion in this announcement is seen as partial recognition that the previous tightly curated store model was too limiting.

Privacy, Trust, and Accounts

  • Strong resistance from many to using an OS from an ad/tracking company; gaze tracking, telemetry, and always-on profiling are major worries.
  • Some note Meta accounts are now separate from Facebook and can be pseudonymous, but others point out you still must sign in and accept opaque policies.
  • A few say they will not touch Meta hardware/OS at all, regardless of features.

Use Cases, Adoption, and Skepticism About VR

  • Fans highlight: games (Beat Saber, sims), fitness/boxing, skill training (welding, surgery, manufacturing), and education; some use VR daily and see huge potential.
  • Critics see VR/“metaverse” as still niche, often gimmicky, uncomfortable, and socially isolating; many headsets end up unused.
  • Debate over whether VR/AR is pre‑“iPhone moment” with big upside to come, or a “flying car” category that will never be mainstream.