Product case
DeviceHub Pro
Product Architecture & Development
A control room for live VR shows that makes headset state, per-show routing, pre-flight readiness and fleet operations visible in one place.
01
The Challenge
A live floor cannot depend on an operator wearing every headset to discover the wrong app, a dead battery, a dropped connection or a crossed cue path.
02
My Contribution
- Product architecture and development for the DeviceHub Pro operating model.
- Show-group routing that separates simultaneous performances by OSC input and output ports.
- Pre-flight, fleet identity, batch operations and conservative auto-relaunch behaviour.
03
System & Decisions
HeadsetsLocal NetworkMultiplayer / Shared StateShow ControlOperator
- A failed measurement is not treated as proof that a headset left the show app.
- Device identity follows serial number, UUID and IP history rather than a single address.
- Notification and automated intervention stay separate, with automation off by default.
04
Result
- Fleet status
- One fleet view exposes battery, running application, version, network and connection state.
- Show isolation
- Each show group owns its room, ports and headsets so parallel cues stay isolated.
- Show readiness
- Readiness is based on verified rooms, conflict-free ports and headset acknowledgement rather than operator assumption.
05
Credits
- Product
- Ankh Interaction Design
- Product architecture and development
- Jacki Chen