A headset-ready application
A VR app that runs on the agreed headsets at their native refresh rate, packaged for the Meta Horizon Store, Steam or enterprise sideloading.
Service · Immersive
Commission a virtual reality app for standalone headsets such as Meta Quest and for PC VR through OpenXR. We design for comfort, hold the frame rate the headset demands, and take the build through store submission or private enterprise distribution.
Meta Quest and OpenXR targets
Comfort settings designed in
Frame budget profiled on device
Deliverables
A VR app that runs on the agreed headsets at their native refresh rate, packaged for the Meta Horizon Store, Steam or enterprise sideloading.
Teleport and smooth movement, snap and smooth turning, seated and standing modes, chosen and tuned to reduce motion sickness.
Interactions mapped through OpenXR action sets so they work with tracked controllers and, where suitable, hand tracking.
A documented draw-call, triangle and frame-time budget, with profiling captures from the actual headset rather than a desktop editor.
Store listing assets and compliance checks, or a managed deployment route for fleets of headsets in training and enterprise settings.
Early decisions
Unity or Unreal Engine, based on visual ambition, team skills and target hardware; standalone headsets favour lean rendering either way.
Mobile-class headset chips and desktop GPUs differ hugely, so we decide whether one build serves both or each gets its own quality tier.
Whether users teleport, walk physically within a guardian boundary or move smoothly shapes level design and comfort ratings.
Fixed foveated rendering, single-pass stereo and application spacewarp are enabled or ruled out early because they affect shaders and content.
On headsets with colour passthrough, we decide whether parts of the app blend with the real room or stay fully virtual.
Engagement
We define session length, user posture, play area and who the users are, since a first-time trainee needs gentler design than a gamer.
Untextured spaces are built and tried on the device within days, to check scale, movement and reach before art begins.
Environments, props, audio and interactions are produced against the performance budget, with weekly on-headset reviews.
We run the store’s technical checks or prepare device-management deployment, then support the first users through launch.
Fit
Safety drills, equipment operation or procedures that are expensive, dangerous or rare to rehearse in the real world.
Experiences where being inside a space matters, such as virtual tours, design reviews at true scale or immersive storytelling.
Organisations that control which headsets users wear can design tightly to that hardware and its controllers.
Alternatives
If users need to see their surroundings with digital objects added, phone or tablet AR reaches far more people.
Open registerWhen the core need is many users meeting, owning items and returning to the same world, a metaverse platform engagement fits better.
Open registerFor spatial apps aimed at Apple’s headset and its windowed model, visionOS development is the more direct route.
Open registerOn a monitor, a dropped frame is a stutter. In a headset it can make people feel ill. Standalone headsets run on mobile-class chips and must render two eye views at a high refresh rate, so every scene is built against a strict budget.
We profile on the headset itself from the greybox stage, because the editor on a desktop machine hides most of the problems.
OpenXR is the Khronos standard that lets one application talk to many headsets through a common API. Using it through Unity or Unreal means input bindings and runtime features are described once, and supporting a new headset is mostly testing rather than rewriting.
VR users reach, crouch and turn. Interactive objects must sit within comfortable reach, text needs to be large and placed at a natural viewing distance, and seated users must be able to do everything standing users can. These rules are set in the greybox, not patched later.
Headsets with colour passthrough let an app mix virtual objects with the real room. That opens training and collaboration uses where staying aware of the surroundings matters, but it also changes lighting, anchoring and safety design, so we decide early whether to use it.
FAQ
Mainly Meta Quest devices and PC VR headsets that support OpenXR, such as those used through SteamVR. Building on OpenXR keeps the app portable as hardware changes.
We hold a steady frame rate, avoid moving the camera without user input, offer teleport and snap turning, and test with people who are new to VR, not only experienced users.
Yes. Enterprise apps can be deployed through device management tools or private release channels rather than a public store listing.
Not as is. VR depends on head tracking and stereo rendering. Some content can be reused in a separate phone or web viewer, which we scope as its own build.
Related services
Unity’s XR Interaction Toolkit and OpenXR plugin are a common foundation for cross-headset VR apps.
Open registerArchitectural or automotive visualisation that needs Unreal’s lighting quality on PC VR.
Open registerRecording VR training results into a learning management system so completion and scores are tracked centrally.
Open registerPrimary sources
Dated official documentation, standards, and research that support the factual claims on this page.
The open standard API for virtual and mixed reality runtimes and devices.
Unity’s documentation on XR plug-ins, OpenXR support and device targets.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.