> For the complete documentation index, see [llms.txt](https://t420.gitbook.io/t420/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t420.gitbook.io/t420/desktop-ui-review-current-state.md).

# Desktop UI Review — Current JobCard State

## Verdict

The current desktop expanded job card is **not premium yet**.

It is functional, but visually it now feels too stretched, too empty, and too mechanically laid out. The recent changes solved some mobile issues, but the desktop layout has regressed in elegance.

## Main problems visible on desktop

### 1. Too much horizontal stretch

The Coordinator and Parts Dept dropdowns span almost the full card width. That makes the section feel heavy and awkward rather than precise.

### 2. Mismatch between sections

* Coordinator / Parts Dept controls are full-width
* Bay / Tech are long but not visually integrated with the rows above
* Vehicle is tiny
* Parts button is tiny

So the schedule area no longer reads as one disciplined system.

### 3. Collapse bar wastes vertical space

The Collapse anchor sits in its own band between summary and details. That still feels like dead space on desktop.

### 4. Header-summary area is too left-heavy

All business information is stacked at left while the right side is mostly empty except urgency. The card feels under-composed.

### 5. Schedule block is not visually balanced

The rows do not feel like one operator panel. Right now it looks like:

* long select
* long select
* short pill
* short button

That is not elegant.

### 6. Team assignment rows are too dominant

Coordinator and Parts Dept should support workflow, not visually overpower the core schedule dependencies. On desktop they now feel louder than Bay / Tech / Vehicle / Parts.

## Recommended direction

### Desktop only

1. Tighten the card width behavior visually

* avoid huge near-edge-to-edge control spans where not needed
* use a more disciplined inner content width for operational controls

2. Move Collapse up

* integrate Collapse with the summary boundary
* remove the extra dead band before details

3. Treat Coordinator + Parts Dept as a compact assignment section

* same label width
* same control width
* not full-card width
* visually subordinate to the schedule block

4. Make the schedule block one aligned control system

* Bay, Tech, Vehicle, Parts should feel intentionally designed together
* choose a consistent desktop width language
* if Vehicle and Parts are shorter, they should still feel grid-aligned, not random

5. Rebalance the card composition

* summary/header area needs better spatial composition on desktop
* either give the right side meaningful structure or tighten the content container so the emptiness is reduced

## Bottom line

The desktop UI currently feels more like a stretched mobile logic than a truly designed desktop operations panel.

The next pass should not add more fields. It should restore:

* discipline
* balance
* hierarchy
* compactness
* elegance

without losing clarity.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://t420.gitbook.io/t420/desktop-ui-review-current-state.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.