Branching architecture at scale
Building a VR experience with optional branches requires more than twice the production effort of a linear one. Every branch needs to feel like a complete experience, with its own entry logic, its own visual language, and a clean way back to the main thread.We built the branching architecture so that Maxar's content team could update the 360 case study nodes independently of the core experience. That meant the Control Centre could stay current as Maxar's project library grew, without requiring a full rebuild each time new material was added. Performance across different headset hardware was a consistent requirement. The experience needed to run reliably on a range of VR hardware without quality compromises that would undermine the premium feel of the environment.
