F1 VR Experience

All of it lands on a rectangle someone else is cutting. There is no native Formula 1 experience for a headset. If you want the race in VR today, you are mirroring a desktop or sitting in a virtual cinema — a TV picture with none of the spatial advantages the hardware actually has.

Hardcore Formula 1 fans already know how to watch a race. What they do not know is how a two-hour Grand Prix feels in a headset: neck, battery, attention, and the second the car leaves the middle of the view.

I wrote the brief before I drew the layout. Success meant lasting the race, finding the board, and still watching the car.

Core Concept

Recreating a television inside VR would have been the obvious move. It would also have ignored the platform.

I treated the experience the way a racing game treats a HUD. The broadcast stays in charge. Everything else is spatial: reachable, ranked, and allowed to recede.

The platform augments the stream. It does not replace it.

Constraints

Quest-class headsets were the honest test: largest consumer install base, limited battery, and a field of view that punishes anything you have to hunt for. I treated those as the design strategy from the start.

Iterations

I started on paper: who the layout was for, what a fan reaches for during a stint, and how a window should behave once you can put it anywhere. That sketch is the system in miniature. A fixed center, modular sides, and a rule that content can move without the layout moving.

From paper I took three visual directions to screen. Familiar F1 color and type helped people recognize the sport. Unchecked, they also fought the stream for attention.

F1 BroadcastGeneral RacingVisionOS

• Familiar
• Brand aligned

• Dense
• Visually noisy

• Cleaner hierarchy
• More modern

• Less distinctive

• Spatially native
• Elegant

• Risked prioritizing aesthetics over usability

The window itself went through the same pass. Early chrome was louder than the content. The version that shipped is a quieter shell: one anatomy, reused across every module.

The hybrid that shipped kept the identity, borrowed the logic of a racing HUD, and followed the rules of spatial computing: one anchor, quieter chrome, supporting information that knows it is supporting.

A layout that can take a new module without a new frame needs a vocabulary first. Zones decide where things may land. Windows are the shells. Components are the content. Those three stay independent so a new module does not force a new layout.

Each module is a job a fan already does during a stint: watch the race, check the board, switch an onboard, read a driver, listen to radio. Support sits further out on purpose. Race-control notifications and a world-anchored track map can interrupt you without rearranging the layout you already learned.

LeaderboardRadioCamerasDriverRace control

Standings live in the left zone for the whole race. Position, gap, and compound stay readable at a glance, because the component never has to invent a new place to sit.

Commentary and team radio share one window. Collapse it to a waveform, or open the transcription when you actually need the words.

The camera browser sits under the stream, so switching an onboard is a glance down, not a hunt. Broadcast, onboards, track, and aerial stay in the same strip.

The right zone holds whoever is on screen: driver bio and stats, or the team, without leaving the race. Tabs swap the content. The window stays put.

Flags, safety cars, and fastest laps sit outside the boundary on purpose. They can interrupt you without rearranging the layout you already learned.

Most of the class did not own a headset. I built the same spatial model as a working prototype so they could collapse a panel, switch a camera, and fire a flag instead of watching a recording of me doing it.