Meta and Vercel publish an AI coding template for browser-based VR
The template includes gaze and hand input support, browser previews and Vercel deployment. Developers can simulate the forthcoming Meta VR Glasses before testing on Quest.
Loading page…
The template includes gaze and hand input support, browser previews and Vercel deployment. Developers can simulate the forthcoming Meta VR Glasses before testing on Quest.
Listen to this story
Meta and Vercel’s October 8, 2026 release gives v0 a path into WebXR prototyping and deployment, with the template providing configured Three.js and Vite scaffolding instead of requiring developers to assemble a game-engine project. Teams can edit generated TypeScript, simulate Meta VR Glasses controls on a Mac or PC, then test on Quest 3 or 3S; Meta expects the glasses hardware in spring 2027. Projects can also be packaged as PWAs for Horizon Store submission, though submission does not guarantee approval.
The template preconfigures the WebXR session, rig and scene, and wires gaze and hand input through Meta’s VR Glasses model.
At Meta Connect 2026, workshop attendees prompted, deployed and opened creations in headsets without installing an SDK locally.
A one-click Vercel deployment produces a shareable HTTPS URL that also opens in the Quest browser.
Developers can now describe a VR experience in ordinary language, preview the generated code in a browser and send it to a Quest headset. Meta and Vercel published the Meta Immersive Web SDK template for v0 on October 8, 2026, providing that workflow without requiring a local development setup.
The starting point is a conversation with v0, Vercel’s coding tool. A developer describes the experience, chooses the target and features, and sees the scene render beside the conversation. The template supplies the underlying WebXR setup—the browser-based VR foundation—rather than asking the developer to assemble it first.
Deployment is built into that path. Once the preview looks right, the developer can deploy to Vercel in one click and receive a live HTTPS URL. Opening that address in the Quest browser lets them enter the experience in VR. The same URL can also be shared with a teammate.
Meta says developers used this web track during a hands-on workshop at Meta Connect 2026. Attendees wrote a prompt, deployed the result and opened it in a headset without installing an SDK on their laptops. That demonstration covered the prompt-to-device workflow, not just a scene displayed on a computer.
The template is a TypeScript project built on Three.js and Vite. Meta says developers can read and edit the code v0 produces, with no game engine to learn. Its preconfigured components cover both the VR scene and the route to hosting it:
Developers do not need a headset to begin iterating. Meta says the IWSDK emulator simulates Meta VR Glasses input and field of view on a Mac or PC. They can then move to a Quest 3 or 3S to try the experience on hardware, rather than staying entirely within the desktop preview.
That distinction matters for the template’s newer device target. Meta expects its VR Glasses hardware to arrive in spring 2027, while developers can build and test for it now. The emulator offers a way to work with the planned input and view before that hardware arrives.
Distribution need not stop at a browser link. Meta says the same project can be packaged as an installable progressive web app, or PWA, and submitted to the Meta Horizon Store. That provides a store-submission route from the web project; it is not a promise of store approval.
Loading discussion...
Join the conversation
Explain whether a desktop simulation would be enough to get you started.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.