Immersive training as a content lane.
VR training shouldn’t mean a separate, blind silo. The VR content lane delivers Quest/APK immersive experiences through the same platform as your 2D courses — same dispatch, same xAPI telemetry, same reporting. Add immersive where it helps, without a second system to run.
The VR content lane is in beta. Package upload, the VR session player route, and xAPI telemetry are working today; the deliberate design choice is to keep VR present but not dominant — it’s a lane in the same platform, not a separate product.
Why VR as a “lane,” not a silo.
Most VR training tools are islands: separate uploads, separate tracking, separate reports. The content-lane approach treats an immersive build like any other package — it’s dispatched, launched, and measured the same way, and its xAPI data lands in the same record store. So the move to immersive doesn’t fragment your reporting or double your operational load.
Immersive, on the same rails.
VR package & upload
Upload Quest/APK builds through the same reliable processing pipeline as your SCORM and xAPI packages.
VR session player route
A dedicated headset session route launches the experience and tracks it like any other session.
Same xAPI telemetry
Immersive interactions emit xAPI statements into your conformant LRS — VR data and 2D data, side by side.
Dispatch & deliver
Route immersive content to where it’s needed with the same controls as the rest of your catalog.
Unified reporting
Completion and performance show up in the same analytics and evidence — no separate VR dashboard.
Present, not dominant
VR is a first-class lane, but it never takes over the product — you adopt it at the pace that fits your program.
A lane, not a fork.
VR builds upload as packages, launch through a VR session route, and emit xAPI to the same LRS as your 2D content. That means dispatch, analytics, compliance evidence, and the developer API all apply to immersive content without special-casing — one set of rails for the whole catalog.
- VR package & upload APIs in the same pipeline
- Dedicated VR session player route
- xAPI statements to your conformant LRS
- Dispatch, analytics & evidence apply unchanged
POST /v1/vr/packages { "title": "Forklift Safety", "platform": "quest", "artifact": "forklift.apk" } ← 201 · in pipeline { "vr_package_id": "vr_pkg_3K", "status": "processing" }See the full API →
On the same rails as your 2D catalog.
Add immersive without a second system.
Get a sandbox key and upload a VR build into the same catalog as your courses.