Designing one workspace across home, office, and mobile displays

A useful multi-display workspace should preserve one logical Scene across home, office, and mobile setups. It should not require three unrelated saved layouts that quietly drift apart every time work changes.

The challenge is to separate what the workspace means from the hardware that happens to be attached.

One Scene, three physical realities

Consider a development Scene with eight targets:

• the primary project window;
• a terminal or build surface;
• browser research;
• technical notes;
• communication;
• planning;
• supporting audio;
• a secondary reference window.

At home, those targets might span three displays. At the office, an ultrawide can carry most of the focused work while the laptop display becomes communication space. In a mobile setup, everything must resolve onto one screen without losing the most important relationships.

The applications are mostly the same. The available geometry is not.

Semantic roles are more durable than display IDs

Hardware identifiers can help recognize a known display, but a logical Scene should not depend entirely on a serial number or a historical global coordinate.

Orvial uses semantic display roles such as Primary, Communication, Reference, and Laptop. An Environment maps real displays to those roles. A target can then express where it belongs conceptually.

Roles do not justify guessing. Specialist roles are assigned deliberately, and fallbacks follow bounded, deterministic rules. When the requested role is unavailable, the resolution records whether an exact placement, deliberate fallback, or unavailable result occurred.

Environment variants should inherit

The base Scene holds what is shared. An Environment variant overrides only what differs.

For example, the base Scene can say that the project window is primary, research belongs nearby, and communication should remain visible without dominating focus. The Office variant can specify that Communication maps to the built-in laptop display. The Mobile variant can prioritize which secondary targets remain visible simultaneously.

Adding a new target to the base Scene makes it available to every Environment unless an explicit override says otherwise. This is safer than editing three copies and hoping they remain consistent.

Geometry must be display-relative

Persisting macOS global coordinates as conceptual placement identity makes a layout brittle. A display can move in the arrangement, its usable area can change, or the menu bar and Dock can alter the space available to windows.

Apple likewise warns that an NSScreen visibleFrame reflects current interface settings and should not be cached, because those settings can change between calls.

Canonical placement is therefore normalized and display-relative. Resolution translates that intent into concrete coordinates using the captured spatial basis for the current topology.

Verification compares the final geometry against the same basis used to create the plan. It does not silently move the goalposts after execution.

Fallback is not the same as best effort

A deliberately authored fallback can be deterministic and fully verified. If a Reference display is unavailable and the Scene explicitly permits Primary as a fallback, using Primary is a known resolution result.

Best effort is reserved for genuine capability or reliability uncertainty. Combining these concepts would make it impossible to tell whether the system followed an intentional rule or improvised around a limitation.

Mobile should be composed, not merely compressed

Reducing every desktop window to a tiny tile produces a technically complete but practically useless result. A mobile Environment needs its own meaningful overrides: which targets share space, which remain available but minimized, and which current task receives focus.

The logical Scene remains one workspace. Its physical expression is deliberately recomposed for the smaller Environment.

Topology changes invalidate evidence

When a display connects or disconnects, the spatial world changes. Observations and plans tied to the old topology cannot be treated as current merely because they were collected a moment ago.

Orvial tracks topology generations so an in-flight activation can stop at a safe boundary rather than applying stale coordinates to a new desk. The change is an evidence invalidation, not just another command to queue behind existing work.

In summary

• A Scene captures the logical desired workspace.
• Environments represent Home, Office, Mobile, and other display contexts.
• Semantic roles survive hardware changes better than historical coordinates.
• Variants inherit and override rather than becoming unrelated copies.
• Geometry is normalized and display-relative.
• Explicit fallbacks remain distinguishable from best effort.
• Topology changes invalidate old spatial evidence.

One workspace across many desks is not a matter of squeezing the same rectangles into different screens. It is a matter of preserving intent through deliberate resolution.