The new screens run on the web. Glasses, XR and your business system

An order status can be useful outside the main business application. A phone, terminal or pair of glasses could display it if the underlying rule is accessible independently of the screen. Each new client still needs interaction design, access controls and testing.

Meta’s 14 May 2026 developer announcement provides a concrete example. It introduced two display paths in developer preview, a mobile SDK and Web Apps built with HTML, CSS and JavaScript and delivered through a URL.

The availability story has moved on

The January pause is no longer the full picture. On 23 September, Meta announced expansion to the UK and Canada, with availability in France, Italy and Germany from 13 October 2026. That does not establish Slovak availability, feature coverage or support for your business use case.

Before budgeting a pilot, check the market, account requirements, support and developer interfaces. Being able to build a demo is different from having an operating arrangement your company can maintain.

Battery requirements also deserve procurement attention. The European Commission’s guidance addresses removability and replaceability under Regulation EU 2023/1542. Device-specific duties and derogations need their own assessment. The regulation does not, on its own, establish a ban on these glasses or explain a commercial rollout decision.

Different devices solve different display problems

A short status or next instruction may help a person whose hands are occupied. That is a hypothesis worth testing in a warehouse or field-service task, rather than evidence that a whole business application belongs in the lens.

Samsung describes Galaxy XR as supporting the OpenXR, WebXR and Unity ecosystem. Developers still have to account for input and hardware differences. A web-compatible device does not make every existing page usable unchanged.

RayNeo’s IFA release distinguishes the glanceable iO display from the GT range’s content-viewing use cases. It does not establish that every model provides Meta’s Web Apps interface. A small information display and a virtual monitor are different design briefs.

Put the business rule behind a shared interface

When a screen calculates order status itself, another client can end up implementing the same rule again. An API can expose one result to several clients, provided authentication, failures and data freshness are handled too.

Shopify applied a related separation so agents could run business logic without the UI. We discuss it in the return to native apps. The principle is useful without promising how long a new interface will take.

Test the task before choosing the glasses

Pick a fact somebody needs away from the main app, such as job status or the next task. Display it on a small phone page first. Check whether the person can complete the next step with that information and whether they are allowed to see it.

A failed trial gives you a dependency to investigate. It does not prove the entire system needs replacing. An IT consultation can separate interface work from changes to data and rules. Whether a separate app is worthwhile should follow from the task and the cost of operating it.