powering productive workplaces
latest
Front page
NewsImmersive Work44m · 12:01 GMT · 10 min read

Is Enterprise XR Ready for Its Lifecycle Challenge?

Three developments this week: Meta’s Quest support deadlines, UK scrutiny of camera-enabled smart glasses and funding for smartphone building capture show why businesses must assess immersive technology as long-term workplace infrastructure, not a one-off hardware purchase

An overhead view of a person walking along a continuous circular path of white footprints painted on grey asphalt, casting a long shadow in bright sunlight
Don't get stuck in a hardware loop. With Meta confirming "v2.13 is the final OS release" for older Quests, businesses must treat XR as permanent infrastructure

Enterprise extended reality (XR) strategies have often been shaped by the immediate use case: a training simulation, a remote-assistance programme, a virtual design review or an immersive studio. But the harder question comes after deployment. How long will the hardware receive security servicing? Will the software stack continue to evolve? Can an employer maintain privacy and governance as devices become less conspicuous and more capable?

That lifecycle question is becoming more pressing as immersive technology moves beyond pilots. My recent UC Today analysis of BBC Sport’s XR studio expansion showed how display technology, real-time graphics, tracking and production workflow can become permanent workplace infrastructure rather than a temporary event installation. The same principle applies to headsets, smart glasses and spatial-capture tools: the value is not just in what the technology can do on day one, but whether an organisation can govern, maintain and scale it over time.

This week’s XR news does not point to one uniform market direction. Instead, it highlights three decisions facing enterprise buyers: how to retire ageing headset fleets without disrupting work, how to prepare for possible restrictions on camera glasses and how to assess lower-friction routes into digital-twin data.

TL;DR

  • Meta has set March 2027 as the point at which Quest 2 and Quest Pro devices receive their final operating-system release, with security patches and critical bug fixes ending by the close of 2027.

  • The UK Government is exploring options to restrict smart glasses in certain settings and sales to certain users, but no ban, legal mechanism or timetable has been announced.

  • Amrax has raised a mid-seven-figure euro round to expand smartphone-based building capture, illustrating how spatial-data collection may become more accessible to facilities and construction teams.

Why Is XR Lifecycle Planning Becoming a Workplace Issue?

Immersive workplace technology combines several interdependent layers: the device, operating system, management tooling, applications, network and identity controls, content, data governance and the workflow the technology is intended to support. A failure or end-of-support decision in one layer can affect the usefulness and risk profile of the rest.

For training and frontline teams, this matters because headsets may be deployed across distributed sites and used for tasks with a long content-development cycle. Replacing hardware is not simply a procurement exercise. It can require testing applications, revalidating device management, updating accessories and training materials, moving user accounts and deciding whether existing content will work as expected on the successor platform.

What Is an XR Lifecycle?

An XR lifecycle is the period during which an organisation can obtain, manage, secure and support an immersive device and its software for a defined business use case. It includes more than whether a headset still powers on: it also covers operating-system updates, security fixes, app compatibility, management support and the availability of replacement devices.

That does not mean every older device needs immediate replacement. It does mean enterprises need a documented decision about whether to refresh, migrate or accept the risks of keeping a fleet after feature or security support ends.

What Does Meta’s Quest 2 and Quest Pro Timeline Mean for Fleets?

Meta has confirmed that Horizon OS v2.13 will be the final operating-system release for Quest 2 and Quest Pro, reaching all eligible devices by March 2027. The company says v213 is also the last supported software development kit version for the devices.

Security patches and critical bug fixes are due to continue through the end of 2027. Meta’s developer guidance also says developers can submit new apps supporting the two headsets through December 2027; after that point, new titles will not be offered on Quest 2 or Quest Pro. Developers can continue updating existing apps, but Meta will no longer test new operating-system and software development kit releases against the older devices.

For an enterprise fleet, that distinction matters. An existing training application may remain available and maintainable, but the organisation will be operating on a fixed platform that no longer receives new operating-system capabilities. It should not assume future applications or management requirements will continue to work on those headsets without additional testing.

Key Takeaways for Quest 2 and Quest Pro Buyers

  • March 2027 — final Horizon OS release reaches devices.

  • December 2027 — security patches and critical bug fixes are scheduled to end, while new-app submissions for the headsets also close.

  • After feature support ends — application teams, rather than Meta, will carry more of the testing burden when platform changes elsewhere affect an existing deployment.

Meta’s schedule also creates a more concrete comparison point for organisations that have delayed a headset refresh. Microsoft has previously stated in its HoloLens 2 release notes that November 2024 was its final feature release, with monthly security servicing continuing through December 2027. The products serve different workloads and have different management models, but the shared end date for security servicing makes 2027 a notable planning horizon for enterprise teams running older mixed-reality hardware.

Meta’s managed-device route applies to newer hardware. In its update on Meta for Work, the company said Horizon Managed Services for Quest 3 and Quest 3S is supported until January 4, 2030. That support statement should not be read as extending the Quest 2 or Quest Pro lifecycle. Organisations with older fleets should confirm their own commercial and support terms with Meta or their reseller, particularly where device management is central to the deployment.

How Should Training and Frontline Teams Respond to the Deadline?

The immediate priority is discovery. Teams should establish where Quest 2 and Quest Pro devices are deployed, which applications they run, whether the devices access corporate systems or sensitive data, and which workflows would be interrupted by a migration. This is especially important where a headset fleet is shared across shifts or sites and where training content has been developed by an external supplier.

Next, buyers should test successor hardware against real tasks rather than only reviewing specifications. A refresh programme should assess application compatibility, account and identity flows, device enrolment, Wi-Fi performance, hygiene and accessory requirements, content-transfer processes and user comfort. A device that is technically supported may still be unsuitable if it makes a frontline workflow slower or harder to administer.

Buyer Checklist: Planning an XR Fleet Refresh

  • Map every device — identify models, locations, ownership, use cases and the applications installed.

  • Set a migration deadline — do not leave testing until the final security-servicing window.

  • Check management eligibility — confirm which current and replacement devices are covered by the required management and support services.

  • Test business-critical content — validate existing training modules and integrations on the intended replacement hardware.

  • Define the post-support policy — decide whether unsupported devices will be retired, isolated or prohibited from accessing corporate resources.

The wider lesson is that enterprises should separate a device’s residual usefulness from its suitability for a managed workplace estate. A headset may continue to run an existing experience after 2027, but that does not answer the security, application-support or procurement questions facing a business.

Could UK Smart-Glasses Restrictions Affect Workplace Deployments?

Camera-enabled smart glasses create a different lifecycle challenge: not software support, but the durability of the permissions and safeguards surrounding the technology. In a Westminster Hall debate on November 4, Parliamentary Under-Secretary of State for the Home Department Satvir Kaur said the Government was “already looking into options to restrict smart glasses in certain settings and restricting the sale to certain users”, adding that the work was “happening at pace”.

The official Hansard record makes clear that the debate was focused on violence against women and girls, covert filming and technology-facilitated abuse. It was not the introduction of a workplace smart-glasses bill. No specific restriction, legal mechanism or timetable was announced.

However, the minister’s remarks are relevant to employers and procurement teams considering camera glasses for field service, logistics, clinical support, training or remote expert guidance. Organisations cannot assume that a product available for sale today will be acceptable in every workplace or public-facing setting over the life of a deployment.

Why This Matters for Employers

  • Existing restrictions already apply in some settings, including courts and tribunals.

  • The Government said NHS England and the Department for Education were considering wearable technology in relevant settings.

  • Any future rules may change where camera glasses can be used, who can obtain them or what controls are expected around recording.

For now, employers should treat the comments as a policy signal rather than a new rule. The practical response is to build stronger governance before deployment: establish the purpose for capture, make recording clearly visible to colleagues and visitors, limit who can access footage, define retention periods and provide a route for raising concerns.

The Information Commissioner’s Office (ICO) already identifies camera surveillance, including wearable cameras used for health and safety purposes, as a form of worker monitoring in its guidance on data protection and monitoring workers. Its wider guidance on video surveillance is also relevant where personal data is collected through camera-enabled devices.

Can Smartphone Capture Make Digital Twins More Practical?

While headset buyers confront fixed support deadlines and smart-glasses users face a shifting policy environment, spatial-capture vendors are attempting to reduce the cost and friction of creating digital representations of physical workplaces.

Salzburg-based Amrax announced a mid-seven-figure euro funding round led jointly by aws Gründungsfonds and SymbiaVC, with existing investor ArborEleven Ventures and business angels also participating. According to Amrax’s release, the funds will support growth and product development for Metaroom, its smartphone-based spatial-capture platform, as well as sales, partnerships and original equipment manufacturer projects.

Amrax says Metaroom uses LiDAR, computer vision and artificial intelligence (AI) to turn scans captured with an iPhone Pro or iPad Pro into parametric three-dimensional models and two-dimensional floor plans. The company says the output can be exported in more than 40 formats and used with planning tools including products from Autodesk, Nemetschek and Siemens Building X.

The release says Metaroom is used by trade businesses, planners, architects, energy consultants and facility managers in more than 175 countries. It also says Amrax tested its Enterprise Building Capture capability on a 60,000-square-metre German hospital, digitising the site with iPhone Pro devices while it remained in operation. Those claims come from the company’s own announcement and have not been independently verified by UC Today.

What Is Spatial Capture?

Spatial capture is the collection of measurements, images and sensor data from a physical environment to create a digital representation of it. Depending on the platform, that representation may be a floor plan, a three-dimensional model or data that can be used in building-information-modelling and facilities workflows.

The significance for workplace technology is not that a phone replaces every specialist scanner. It is that lower-friction data collection may make it easier for facilities, construction and design teams to begin a digital-twin workflow. Buyers will still need to assess accuracy, export requirements, data ownership, integration with existing systems and whether the capture process is suitable for their buildings and compliance obligations.

What Should Enterprise Buyers Take From This Week?

These announcements concern different parts of the immersive workplace: device lifecycles, wearable-camera governance and spatial data. Yet they point to the same procurement reality. XR cannot be evaluated only through a product demonstration or an initial pilot outcome.

A resilient deployment requires a support horizon that matches the business case, a migration path before a device becomes unsupported, governance proportional to the data it collects and a clear understanding of which claims are independently verified and which come from suppliers. The technology may become more ambient and easier to deploy, but the operational responsibilities do not disappear with the headset, glasses or smartphone.

As XR becomes part of the workplace infrastructure stack, the important question is no longer simply whether an experience is immersive. It is whether the organisation can sustain, secure and govern it for as long as the work requires.

rate this story
helps rank stories across uc today
Join the conversation

Does this reflect your experience?

opening the room…