Desktop Layout Modes
Prox OS now has six desktop layout modes. They are not competing products; they
Prox OS now has six desktop layout modes. They are not competing products; they are different renderers for different work styles.
OS Desktop
Purpose: familiar app/window/folder workspace.
Mental model: a browser-native operating system desktop.
Best use cases: long-running app windows, multiple virtual desktops, Mission Control, dock workflows, titlebar window management.
Supported surfaces: desktop icons, windows, dock items.
Current v0: existing Prox OS window manager and virtual desktops.
Future direction: cloud-backed layout sync and richer Space persistence.
What it is not: a simple website navigation page.
Atlas Desktop
Purpose: OS-level launcher and home dashboard.
Mental model: start from apps, Spaces, recents, search, and recommendations.
Best use cases: choosing the next app, scanning available surfaces, presenting Prox OS as a home workspace.
Supported surfaces: Atlas cards, desktop icons, Switchbar targets.
Current v0: polished launcher with search copy, featured app cards, and Space recommendations.
Future direction: personalized recommendations and installed surface groups.
What it is not: another App Store or a WebCatalog clone.
Canvas Desktop
Purpose: relationship-first workspace.
Mental model: apps, Spaces, data sources, AI agents, links, documents, and workflows as nodes in a graph.
Best use cases: understanding context, designing workflows, mapping project dependencies, showing AI context relationships.
Supported surfaces: Canvas nodes.
Current v0: React Flow graph with nodes, edges, minimap, controls, background, drag, and zoom.
Future direction: persisted graph placement, node-specific previews, and workspace data bindings.
What it is not: a replacement for every app window.
Grid Desktop
Purpose: widget dashboard and enterprise workbench.
Mental model: a dashboard of small app surfaces that can be rearranged.
Best use cases: daily operations, metrics, tasks, weather, calendars, visitor signals, pricing, activity, and Space status.
Supported surfaces: Grid widgets with preferred sizes such as 1x1, 1x2,
1x3, and 2x2.
Current v0: draggable react-grid-layout widgets with local runtime layout
state.
Future direction: persisted grid layouts per Space, team, or profile.
What it is not: a full BI dashboard backend.
IDE Desktop
Purpose: production workbench.
Mental model: VS Code-like shell with explorer, center work area, inspector, and bottom logs/tasks.
Best use cases: building, reviewing docs, inspecting app metadata, tracking quality checks, and working with AI context.
Supported surfaces: IDE panels in left, center, right, or bottom regions.
Current v0: react-resizable-panels layout with explorer, work area, context
inspector, and bottom log panel.
Future direction: persisted panel layouts, tabs, and task-aware workbench states.
What it is not: a complete code editor or GoldenLayout clone.
Immersive Desktop
Purpose: one app surface visually owns the workspace.
Mental model: enter a raw product surface while keeping a clear OS return path.
Best use cases: product demos, analytics rooms, focus sessions, presentation surfaces, media, games, and future raw app modes.
Supported surfaces: Immersive surfaces.
Current v0: minimal chrome preview with a return-to-OS action and app surface summary.
Future direction: focus policy, notification handling, active app selection, and immersive layout persistence.
What it is not: browser Fullscreen API, ordinary maximize, or a guaranteed desktop-client capability.
Virtual Desktop Scope
Virtual desktops currently belong only to OS Desktop. Other modes are renderer previews and do not yet participate in the existing Spaces / Mission Control system.