Spatial computing

The screen was never the point

Vista is the product page for a device that does not exist: a full-bleed stage, a feature rail you scroll rather than one that scrolls itself, and a silicon panel that states its numbers plainly.

A pale dune landscape under a soft gradient sky, used as an immersive environment

A closer look

01

An display for every task

Two panels the size of a postage stamp carry more pixels each than a 4K television, so text stays text at any distance.

02

Input without hardware

Look at a control and pinch. No wand, no glove, nothing to charge on a second cable overnight.

03

Sound that stays put

Audio is placed in the room rather than in your ears, so a window you moved to the left still sounds as though it is there.

04

Environments on demand

Replace the room with a landscape when you need to concentrate, and dial it back when somebody walks in.

05

Privacy at the sensor

Eye data never leaves the device and is never handed to an app. What you looked at is not a signal anybody else receives.

06

Passthrough that convinces

Cameras rebuild the room with low enough latency that reaching for a cup is not a calculation.

Silicon

Two chips, one of them doing nothing but listening

One runs the system. The second does nothing but process twelve cameras, five sensors and six microphones, so the picture is on the panels before your inner ear notices the delay.

Sensor-to-photon latency
12 ms
Cameras and sensors
17
Pixels across both panels
23M
Refresh, sustained
90–100 Hz
A processor lit from beneath on a circuit board

What this theme is

Vista is the front page of a spatial-computing product that does not exist. The specifications, the latencies and the pixel counts are illustrative: they are here to exercise the components, not to describe a real device.

The category it belongs to — flagship hardware marketing — conventionally opens with a full-bleed photograph and lays the headline across it. Vista puts the headline above the photograph instead. Text on a photograph cannot be contrast-checked, and a landscape whose brightness varies across its own width is the worst possible ground for it.

What is different about it

The feature rail scrolls, it does not play. Anything that moves for longer than five seconds needs a way to stop it under WCAG 2.2.2, and a list of six features has no reason to move on its own. It is an ordinary scroll region with a name and a tab stop, so a trackpad, a drag, the arrow keys and the two buttons all reach the same content. The buttons disable themselves at each end rather than looking live and doing nothing.

Ask us anything about it

The device is fictional. The page architecture, the colour system and the gates behind them are not.