NEW TO THIS? START HERE
Why VR as a “lane,” not a silo.
Keep immersive package metadata in the same catalog while validating the delivery path that its device and package type support. Instrument the experience to send xAPI events, then verify identity mapping and completion before using those records in reporting.
- Safety & hands-on skills training
- Providers adding an immersive offering
- Enterprises piloting VR at scale
What you control
Immersive, on the same rails.
VR package & upload
Register supported immersive package artifacts through the VR upload and registration APIs. Package limits and delivery options require validation for your build.
VR session player path
A dedicated VR player path is available for integration testing. Validate launch, resume and device behavior before rollout.
Instrumented xAPI telemetry
Your experience must instrument and send its learning events. Validate accepted statements and learner identity before relying on the resulting records.
Dispatch & deliver
Choose the delivery path supported by the package type and target device. SCORM dispatch parity for arbitrary APK builds is not established.
Unified reporting
Reporting depends on the events actually received and the identity mapping used. Verify completion and evidence semantics in the pilot.
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.
FOR THE TECHNICAL BUYER
A lane, not a fork.
Use a bounded pilot to validate artifact registration, target-device launch, instrumented events and persisted learning records. Available delivery controls depend on the package type; immersive playback does not automatically create skill mastery or completion evidence.
- VR package & upload APIs in the same pipeline
- Dedicated VR session player path
- Instrument and validate xAPI statements
- Verify delivery controls and completion records
Beta pilot checklist
1. Register the uploaded package artifact
2. Validate launch and resume on the device
3. Instrument and verify xAPI events
4. Reconcile completion and learner identityStatus, limits and plans
- Status
- Beta
- Plans
- VR uploads follow your plan’s package and storage limits. See plans
- Limits
- Meta Quest and Android VR APKs
- Validate devices and content before deployment
- Activity from instrumented content via xAPI
- Docs
- Upload your first SCORM package
Questions about VR content lane
Can I host VR training?
Which headsets are supported?
How is VR activity tracked?
PAIRS WITH
Works with
- Available
SCORM Dispatch
Review SCORM dispatch separately for compatible course packages.
- Available
Analytics & completion
Understand the reports available for verified learning records.
- Available
xAPI 2.0 LRS
Review the xAPI 2.0 conformance test results and integration requirements.