XRVuer
A workstation UI for picking inspection jobs, reviewing X-ray images, and taking new shots without guessing whether the system is ready
UI/UX
Product Design
Role
Design direction (Figma build assisted)
Timeline
[TBD]
team
1 designer (direction + review)
platform
Desktop workstation

What this is for
Factories and inspection teams use industrial X-ray to look inside metal parts — welds, housings, blades — without cutting them open. XRVuer is the desktop workstation for that work: find the right job, open its images, and when needed capture new X-rays into a standard industrial format.
The people using it are operators and inspectors under time pressure. A wrong setup can waste a shot, scramble a study, or leave the system in an unsafe state. The product has to make readiness obvious, not bury it in settings.
The harder problem — taking a new shot
Once you need a new acquisition, the old flow did not match how the real detector behaves. Operators could start live view or capture without knowing if calibration matched, if the detector was healthy, or what to do when something failed. Faults often only showed up in a log — not as a clear recovery path on screen.
From the live prototype (not a lab study): a first shot took roughly nine clicks, plus a long detour if no matching calibration existed. The UI only showed a few detector states while the backend had many more.
What we redesigned
We treated acquisition as a gated story, not a pile of buttons:
Get the detector ready while job setup runs in parallel
Meet at Arm — only then allow exposure
Capture, review image quality, then finish or export
Cover fault and override paths in the same prototype, not as afterthoughts
Separately, Section 1 cleaned Study List to Viewer so picking a job and reading images feels like one product, not two apps glued together.
Safety, in plain terms
A human-factors pass set rules that stayed in every prototype version:
Never paint ready as green unless every check actually is
Arm only when the mode needs it; say clearly when X-ray is on, auto-detect is on, or you are in dark (no X-ray) capture
Put Stop and Discard where they will not be confused; keep a short undo window
If Arm is blocked, say why — do not leave a dead button
Where the day starts — Study List to Viewer
Section 1 of the project redesigned the front door of the product:
Study List — a worklist of past and current inspections (filter, sort, pick a job)
Launch into the Viewer — open that job to inspect images, measure, and review quality
Layouts — how side panels, image stage, and tools share the screen once you are inside
This is the path most people hit first: what am I inspecting today? — before anyone talks about detectors or exposure.
Status and next
What is real today: high-fidelity Figma covering Study List to Viewer and the full Acquire path with fault branches. Click-path estimates look shorter when readiness and job setup meet at Arm — that is a redesign estimate, not a measured field result. No operator testing yet, so no conversion or site metrics.
Next: polish the Acquire chrome, decide which Section 1 patterns carry into later UI kits, and validate with operators once the prototype is stable.
Naming note: confirm NDA before public publish for product, vendor, or backend names.

