Jarvis Desktop today is a good shell wrapped around two products that brought their own shells with them. Open Jarvis Design or Jarvis Team and the outer navigation disappears, the type scale changes, the accent colour changes, and you lose the thread of where you were. Each proposal below fixes that a different way, then carries the fix across the whole bundle — Chat, Apps, Projects, Design, Team, Scheduled Tasks, the Issue Board, Deployments and Settings.
These are not palette swaps. Each direction takes a different position on the shell itself — where navigation lives, whether operational state is ambient or on demand, and how dense the working surface should be — and then derives typography, spacing, geometry, iconography and motion from that position. Every preview below is the real prototype, running live.
The desktop sidebar, Jarvis Design's sidebar and Jarvis Team's sidebar are three separate navigation systems with three different logos, type scales and accent colours. Entering an inner product replaces the outer one entirely, so context is lost at exactly the moment you need it.
Scheduled Tasks, the Issue Board and Deployments hold everything that is running unattended, but nothing about their state surfaces anywhere else. A failed deployment and a skipped scheduled run look identical from the Chat screen: like nothing.
Most captured screens were empty, and the empty states are a grey tray icon and four words. There is no path forward from them and no explanation of what would fill them — which makes a healthy first run look like a failed install.
Image digests, source snapshots, provider revisions and deployment refs are set in the body face and truncated mid-hash. These are strings operators compare character by character against a terminal.
Secondary text sits near the floor of legibility on the dark surface, page titles and section titles are nearly the same size, and disabled and enabled controls are hard to tell apart — so nothing on the page claims priority.
Chat, Design, Build and Team are the four modes the entire product is organised around, and the only way to see them is a small chevron next to the app name. Every proposal promotes this control and keeps your place when you use it.
⌘K / Ctrl-K for search, ⌘B to collapse navigation, Esc to close anything.Every prototype carries a bar at the bottom of the window. It is review chrome, not part of the design: it switches direction, flips the screen state, toggles light/dark, and links to the specimen, the comparison and this page.
Nothing talks to a backend. Sending a message, deploying, signing out, installing a harness and every destructive action are inert and answer with a toast. All content is drawn from the 2026-07-26 capture; where the capture showed an empty product, the prototype also carries a realistic populated state so the layouts can be judged when full.