Skip to content

Service · Immersive

VR App Development Services

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

What a VR app development engagement delivers.

01Delivered

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.

02Delivered

Comfort and locomotion options

Teleport and smooth movement, snap and smooth turning, seated and standing modes, chosen and tuned to reduce motion sickness.

03Delivered

Input for controllers and hands

Interactions mapped through OpenXR action sets so they work with tracked controllers and, where suitable, hand tracking.

04Delivered

Performance budget and profile

A documented draw-call, triangle and frame-time budget, with profiling captures from the actual headset rather than a desktop editor.

05Delivered

Distribution set-up

Store listing assets and compliance checks, or a managed deployment route for fleets of headsets in training and enterprise settings.

Early decisions

Technical decisions we settle early in VR app development.

01Decided

Engine choice

Unity or Unreal Engine, based on visual ambition, team skills and target hardware; standalone headsets favour lean rendering either way.

02Decided

Standalone, PC VR or both

Mobile-class headset chips and desktop GPUs differ hugely, so we decide whether one build serves both or each gets its own quality tier.

03Decided

Locomotion model

Whether users teleport, walk physically within a guardian boundary or move smoothly shapes level design and comfort ratings.

04Decided

Rendering features

Fixed foveated rendering, single-pass stereo and application spacewarp are enabled or ruled out early because they affect shaders and content.

05Decided

Mixed reality passthrough

On headsets with colour passthrough, we decide whether parts of the app blend with the real room or stay fully virtual.

Engagement

How a VR app development engagement runs.

  1. 01Phase 1

    Experience and comfort brief

    We define session length, user posture, play area and who the users are, since a first-time trainee needs gentler design than a gamer.

  2. 02Phase 2

    Greybox in the headset

    Untextured spaces are built and tried on the device within days, to check scale, movement and reach before art begins.

  3. 03Phase 3

    Content and interaction production

    Environments, props, audio and interactions are produced against the performance budget, with weekly on-headset reviews.

  4. 04Phase 4

    Certification and rollout

    We run the store’s technical checks or prepare device-management deployment, then support the first users through launch.

Fit

When a VR headset app is the right choice.

01Good fit

Training in risky or costly settings

Safety drills, equipment operation or procedures that are expensive, dangerous or rare to rehearse in the real world.

02Good fit

Presence is the product

Experiences where being inside a space matters, such as virtual tours, design reviews at true scale or immersive storytelling.

03Good fit

A defined headset fleet

Organisations that control which headsets users wear can design tightly to that hardware and its controllers.

Frame rate is a comfort requirement

On 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.

Building on OpenXR

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.

Designing for bodies, not screens

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.

Passthrough changes the brief

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

Questions to resolve before the build.

01Which headsets do you build for?

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.

02How do you prevent motion sickness?

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.

03Can we distribute the app privately to staff?

Yes. Enterprise apps can be deployed through device management tools or private release channels rather than a public store listing.

04Can the same app run on phones?

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.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
    Khronos Group: OpenXR

    The open standard API for virtual and mixed reality runtimes and devices.

  2. 02
    Unity Manual: XR

    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

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.