AR & VR Development Company in Birmingham

Asset production, not engineering, is where Birmingham immersive budgets actually go. Projects size as a scoped AR or VR proof of concept at Birmingham rates from a regional agency over eight to fourteen weeks, covering a single hardware target (typically Quest 3) and a baseline interaction loop, a production-grade single-platform application (training simulation, surgical rehearsal, retail try-on) including content production, motion-sickness validation, and Meta Horizon Store or App Lab submission, or an enterprise-grade build with multi-headset support (Quest 3, Vision Pro, HoloLens 2, PICO), PLM or LMS integration, and MDM packaging via ArborXR or ManageXR. Photoreal Unreal Engine 5 automotive design review or architectural visualisation sits at the upper end because the asset pipeline (CAD tessellation, Nanite optimisation, Lumen lighting) carries real production weight.

UK GDPR treats biometric data used for unique identification as special category personal data under Article 9, and the ICO has been clear that eye tracking, gaze pattern data, hand tracking, body skeleton tracking, and inferred emotion from facial expression are sensitive forms of processing even where identification is not the explicit purpose. Every XR build we deliver opens with a Data Protection Impact Assessment under Article 35 (mandatory rather than optional here), a Legitimate Interests Assessment or explicit consent capture, and a privacy notice that names every sensor stream — inside-out tracking, eye tracking on Quest Pro or Vision Pro, hand tracking, body tracking, room scanning — and the retention period for each. Spatial anchors are stored in UK-resident Azure Spatial Anchors or ARCore Geospatial. Children's XR (under-18s) falls under the ICO Age Appropriate Design Code with high-privacy defaults and no behavioural advertising.

Partially yes, and the trade-offs matter. Unity 2022 LTS or Unity 6 with the XR Interaction Toolkit 3.0+ and OpenXR runs cleanly on Quest 3, Quest 3S, PICO 4 Enterprise, and HoloLens 2, sharing the bulk of interaction logic. Apple Vision Pro is the awkward one: visionOS supports a Unity PolySpatial path for shared-immersive content, but bounded volumes and the fully-immersive RealityKit shell behave differently enough that we typically run Vision Pro as a parallel native build in Swift, RealityKit, and Reality Composer Pro when the use case justifies the device. HoloLens 2 uses MRTK 3 on Unity or Babylon.js for WebXR. We will scope the device matrix in discovery and only commit to a one-codebase plan when the interaction model genuinely supports it — most enterprise builds in Birmingham target Quest 3 and HoloLens 2 first, with Vision Pro added when the buyer or training audience justifies the hardware spend.

Yes, this is a core competence for the Birmingham practice. AR-guided assembly typically targets HoloLens 2 first because it is hands-free, certified for industrial environments, and dominant in West Midlands automotive. We integrate with Siemens Teamcenter, PTC Windchill, or Dassault 3DEXPERIENCE PLM so the work-instruction step-list is sourced from the same engineering bill of materials shop-floor supervisors already trust. CAD ingest uses Pixyz or CAD Exchanger for tessellation and decimation. Anchoring uses Azure Spatial Anchors (UK South), QR fiducials, or VPS markers. Multi-headset MDM is ArborXR, ManageXR, or Microsoft Intune. VR training runs on Quest 3 with PICO 4 Enterprise as a managed-fleet alternative. Every shop-floor deployment ships with an ISO 45001 occupational health and safety risk assessment for headset use, fatigue, and motion sickness.

Motion sickness is the single largest reason XR pilots fail to scale, and it is design-led, not hardware-led. We design at a stable 72Hz on Quest 3 baseline (90Hz where the GPU budget supports it), respect Meta and Apple comfort guidance on acceleration and snap-turn versus smooth-turn, default to teleport locomotion for novice audiences, and avoid camera moves the user does not initiate. We document and ship a session-time recommendation appropriate for the audience — typically twenty to thirty minutes for novice clinical or educational users — and build break prompts into the application loop. Clinical builds (Queen Elizabeth Hospital, UHB NHS Foundation Trust) carry a pre-screening flow that excludes users with vestibular conditions or recent concussion, and ship with a clinician-facing observer view. Children's experiences under-13 follow the manufacturer's own age guidance (Meta's age policy raised the floor to 10 in 2023) plus the ICO Age Appropriate Design Code.

We default to AWS eu-west-2 (London) as primary and eu-west-1 (Ireland) as DR for resilience and lower latency. Azure UK South (London) plus UK West (Cardiff) is the resilient UK-only pair when the client requires UK-sovereignty — most JLR-adjacent, HSBC-adjacent, and NHS-adjacent clients land here because their enterprise tenancy is already Microsoft 365. Azure Spatial Anchors persists spatial maps in UK South. Cloud rendering via NVIDIA CloudXR or PureWeb is deployed in eu-west-2 or UK South. Meta Horizon and Vision Pro App Store binary distribution is global by platform design, but every backend service, asset CDN, and analytics pipeline can be pinned UK-only. NHS workloads are wired to Data Security and Protection Toolkit standards at provisioning time, not retrofitted.

It depends on the build. The Video Games Expenditure Credit (VGEC), which replaced the Video Games Tax Relief from April 2024, is available for genuine video games — including some XR games — passing the BFI cultural test, with a 34 percent credit on qualifying core expenditure. Industrial training simulations, surgical rehearsal, retail try-on, and architectural visualisation do not typically qualify for VGEC but generally do qualify for the merged UK R&D tax credit scheme (20 percent above-the-line expenditure credit from April 2024, with a 27 percent net rate for R&D-intensive loss-making SMEs at the 30 percent threshold). Eligible activity includes resolving technological uncertainty (real-time rendering, novel interaction models, sensor fusion, occlusion handling), not routine asset production. We deliver the Additional Information Form documentation HMRC has required since August 2023.

A typical Birmingham industrial training VR application targeting Quest 3 takes fourteen to twenty-two weeks from kickoff to managed-fleet deployment, assuming the work-instruction content and PLM integration are ready. Week 1 to 3 is discovery, DPIA under Article 35, hardware matrix decision, and architecture. Week 4 to 12 is core Unity XR build, content production, and motion-sickness validation cycles. Week 13 to 18 is enterprise packaging via ArborXR or ManageXR, MDM fleet rollout, and pilot with shop-floor or clinical users. Week 19 onward is iteration on observed metrics. Multi-device builds (Quest 3 plus HoloLens 2 plus Vision Pro) add four to eight weeks because of the visionOS RealityKit parallel build. Photoreal Unreal Engine 5 design-review applications run twenty-four to thirty-six weeks because the CAD tessellation and Lumen lighting pipeline carry significant production weight.