Vision

What happens when remote desktop meets spatial computing

A flat monitor forces every window to share one plane at one distance. Headsets like Apple Vision Pro give every window its own depth. For remote desktop — a product whose whole job is moving another machine's screen onto yours — that is not a feature, it is the next surface.

The flat monitor is a compromise we stopped questioning

Think about how you use your computer right now. You have a screen — maybe two if you are lucky — bolted to a desk or balanced on a lap. You are staring at a flat rectangle of light, and every piece of your work happens inside that rectangle.

That has been the deal for forty years. More pixels, thinner bezels, better colors — but always a rectangle. Always a fixed amount of screen real estate. Always a physical object taking up physical space at one fixed distance.

Spatial computing breaks that contract entirely. Your screens are not objects anymore. They are ideas placed at the depth where they belong: tools within arm's reach, the editor at desk distance, reference docs floating farther back, ambient widgets at the wall.

For most apps, that is a nice-to-have. For remote desktop — a product whose entire job is moving another machine's screen onto yours — it is a paradigm shift.

How depth reorganises a workspace

The single most underrated thing about spatial computing is not the size of the windows. It is the depth. Humans already layer attention by distance every day — the notebook in your hand, the laptop on the desk, the meeting room across the office. Flat monitors force all of that into a single plane.

Here is what a remote-desktop workspace looks like when you stop pretending depth does not exist.

A workspace, laid out by depth
ZoneDistanceWhat lives there
Arm's reach~30 cmTools, palettes, scratch notes. Inspector panels, color pickers, a sticky for the next idea. Touch-close, glanced at constantly, never the centre of focus.
Desk distance~60 cmEditor, terminal, the focused workspace. The remote Mac's desktop, sized like a comfortable 32-inch monitor. The single surface your eyes spend ninety percent of the day on.
Peak space~2 mReference docs, video calls, monitoring. API docs in one window, a Zoom feed in another, a dashboard you check every few minutes. Visible without dominating, ignorable without closing.
Ambient~4 m+Music player, calendar, slow widgets. Things that should exist but never grab your eye. The background instruments of a working day, where they cannot crowd what matters.
InfiniteBeyondThe room, the sky, the skybox itself. The environment around the work. Apple's Mount Hood, a quiet cafe, a black void. The backdrop that decides whether you feel calm or boxed in.

The flat monitor is a compromise we stopped questioning. Spatial computing finally asks the right question — at what depth does each window belong?

— Remio team, on what changes when the screen leaves the desk

Why remote desktop gets better in space

Remote desktop has always been constrained by the client device's screen. You are accessing a powerful Mac or PC, but you are viewing it through whatever display you happen to be holding — a 13-inch laptop, a 10-inch iPad, a 6-inch phone. You are looking at your desktop through a keyhole.

Spatial computing removes the keyhole. The host's resolution is unchanged. The decoder is the same. What changes is the surface: instead of a bezel-bound rectangle, the stream lands at whatever size, position, and depth feels right.

macOS already supports Mac Virtual Display on Vision Pro — you can extend your Mac's display into visionOS as one or several additional monitors. Apps like Immersed have demonstrated multi-screen virtual workspaces. The pieces are here. What is missing is a remote-desktop experience that was designed for this surface, not bolted on top of an iPad app.

The current landscape

Today, if you want to use your remote computer in spatial computing, your options are limited:

The gap is clear: nobody has built a remote desktop app that treats spatial computing as a first-class platform rather than an afterthought.

Why native SwiftUI apps have the advantage

Here is where architecture decisions made years ago start paying unexpected dividends.

visionOS is built on SwiftUI. Not "supports" SwiftUI — it is built on it. Window management, the gesture system, the spatial layout engine, the eye-tracking interaction model — all of it is SwiftUI-native. Apps written in SwiftUI adopt visionOS features naturally. Apps written in other frameworks have to fight the platform.

Remio is 100% SwiftUI on Apple platforms. That was not a decision made with Vision Pro in mind — when we started building, Vision Pro was still a rumor. We chose SwiftUI because it was the right tool for building a native iOS and macOS app. But the consequence is significant: porting Remio to visionOS becomes a natural extension of the existing codebase, not a rewrite.

Our streaming pipeline uses Metal for hardware-accelerated video decoding. Metal runs on visionOS. Our input handling is built on Apple's gesture recognizer system, which extends to hand tracking. Our UI components use SwiftUI's layout engine, which already understands spatial windows and volumes. None of that is theoretical — it is the same Swift package, recompiled.

Compare this to Electron-based remote desktop apps. To ship on visionOS, they must either run as a flat compatibility window — losing everything that makes the platform interesting — or rebuild their entire rendering pipeline for a platform that does not have a web browser engine at the system layer. The native path is the only path that leads somewhere interesting.

What spatial remote desktop could look like

We are not shipping a visionOS app today. But here is the experience we are designing toward:

The hardest part is not the rendering — it is making the interaction feel natural. A remote desktop that requires you to think about latency is not a remote desktop worth using in spatial computing. The hand-tracking-to-cursor pipeline must feel as immediate as touching glass. That is exactly the problem Remio's streaming pipeline has been solving on flat screens for years.

We did not plan for spatial computing. But by building native, we accidentally built a foundation that is ready for it.

Remio's path forward

We are not going to rush a visionOS app to market. The installed base is still small, the interaction patterns are still evolving, and Apple ships meaningful visionOS updates every year. Developer tooling gets substantially better with each release.

What we are doing is building with visionOS compatibility in mind. Every architectural decision we make for iOS and macOS is evaluated against the question: will this work in a spatial context? Our SwiftUI views, our Metal rendering pipeline, our gesture handling — all of it is being built in a way that ports cleanly when the time is right.

When the hardware reaches a tipping point and the interaction patterns stabilize, Remio will be ready. Not as a flat app running in compatibility mode, but as a spatial-native experience that uses the full depth of visionOS.

The flat monitor was always a compromise. We are building for what comes after.

Remio app icon

Try the foundation today

Remio is free, native on every platform, and end-to-end encrypted. Feel what a real low-latency remote desktop is like — the same pipeline that will carry into spatial computing when the time is right.

Free foreverNative SwiftUIEnd-to-end encrypted