Meta's new template preserves a path from web prototype to installable app. Understand how to plan distribution without creating two product bases.
Direct answer
According to Meta, the project created with the IWSDK template for v0 can start as a WebXR experience accessed via URL and then be packaged as an installable PWA for submission to the Meta Horizon Store. Continuity reduces rework between validation and distribution, as long as the team treats manifest, cache, update, permissions, offline mode, security and store requirements as product steps, and not as a simple export button.
One base does not mean a single channel
The same code can support link access and installation, but each channel has its own expectations for discovery, update, authentication and support.
PWA requires upgrade contract
Define how service worker, cache and immutable assets receive new versions. An XR session cannot depend on incompatible files stuck on the device.
The store adds requirements and trust
In-store distribution can improve discoverability and recurrence, but requires metadata, policies, testing, versioning, and a review process.
Metrics must separate acquisition and use
Compare URL opening, VR entry, return, installation, session completed, and conversion. An unused installation does not prove value.
Nexus Reading
Plan web and PWA as stages of the same journey: rapid prototype, observable pilot and distribution only when retention and operations justify it.
FAQ
Does any WebXR automatically become a PWA?
No. The project needs a suitable manifest, service worker, icons, caching strategy, security and compatibility.
Is it better to start with the store?
To validate a hypothesis, a URL usually reduces friction; the store makes more sense when installation, discovery or recurrence add value.
Is it necessary to maintain two projects?
The goal is to share the base, but channel configurations and specific tests remain necessary.
Essential guides to delve deeper into the decision
This editorial analysis was produced by Nexus from the official sources below, consulted on October 8, 2026. The text is original and interprets practical implications for companies.
- Meta Horizon OS Developers — Build for Meta VR with v0 by Vercel: Official statement regarding URL, Quest Browser and packaging as PWA.
- Meta Horizon Store — Publishing: Official guidance for preparing and publishing web applications in the Meta ecosystem.
Date reported by the main source: October 8, 2026.