Insights · guide

Freeze headset updates before your XR event

Drafted with Insight · edited by The WE ARE VR team

development

A headset update is a change request wearing a friendly button.

I wrote this because event teams often test the experience, then forget the device around it. A stable build can still fail when one headset changes overnight.

What's the problem?

An event headset is a small stack of moving parts. It has an operating system, the software controlling the device, plus your app, controller software, permissions, login state and network settings.

Any one of those can change between rehearsal and doors opening. An update can alter boundary setup, controller behaviour, casting, permissions or the way an app launches. The update may be fine. Your timing is the problem.

Jozi activations add ordinary venue pressure. Load-in runs late. Corporate Wi-Fi needs another approval. The client wants a final logo change. Someone connects every headset to the venue network, and three devices begin downloading while guests arrive. (Machines also enjoy deadlines.)

The worst case is an uneven fleet. Seven headsets run the tested state. The eighth runs something newer, so its failure appears random.

What's the solution?

Use one device state sheet, then set a software freeze before activation day. A freeze means nobody changes the app or device software without repeating the agreed test.

Give every headset a visible asset label, such as JHB-XR-01. Add one row per device to a shared sheet. Record the headset model, operating system version, your app version, controller status, login account, network name, test date and tester initials.

Where the platform allows it, pause automatic updates. Still record the versions. Settings can be missed, and some update controls are limited.

Set the freeze at least three working days before doors open. During that window, install the final build on every device. Restart each headset fully, launch the experience, complete one normal session, exit, reset and launch again. Test casting and networking if the event uses them.

Test every headset. Teams sometimes rely on one preferred test unit, often called the golden device. It is useful for comparison, but it cannot prove the rest of the fleet matches.

Picture an eight-headset activation in Sandton on Friday. On Monday, you label H01 to H08 and install the chosen build. On Tuesday, your sheet shows H06 has a different system version. You update the others or isolate H06, then test the chosen state again. On Wednesday, the whole fleet completes a cold-start rehearsal. Thursday is reserved for fixes; new features wait.

If a client requests a late content change, the choice is plain: retest every affected device or move the change to the next activation. A small visual tweak can still create a new build, and a new build needs a test.

Keep the spare headset in the same state too. A spare running different software is another problem in a protective case.

What's next?

  1. Create a simple device state sheet and label every headset this week.
  2. Pick a freeze date for your next activation and share it with the client.
  3. Run one cold-start session per device, then mark each row pass or fail.

Share your device sheet with the Jozi XR community, or ask us what to record.

The WE ARE VR team