Immersive training as a content lane.
The VR content lane is in beta. Store an immersive build beside your other packages, then validate delivery on the intended device. xAPI telemetry depends on events instrumented by the experience; completion and reporting require a verified integration.
The VR content lane is in beta. Package handling and a dedicated player path exist, but headset compatibility, event instrumentation, suspend/resume and completion must be validated for each delivery setup. A device name is not a certification.
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.
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.
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 identityReview the API →On the same rails as your 2D catalog.
Add immersive without a second system.
Review the beta path and plan requirements before starting a device-specific pilot.