feat: phase 2.1 — multi-tab desktop dashboard (Dashboard / Compare / Progress / Settings) #2

New issue

Open

opened 2026-05-15 04:53:48 +00:00 by hartle-tech · 0 comments

hartle-tech commented

2026-05-15 04:53:48 +00:00

(Migrated from github.com)

S01E11 — The Dashboard Era

Current GUI is a 5-screen state machine on one viewport. The v2 design system (see `assets/mockups/playful_ui_design_for_dumpsock_v2.png`) calls for a multi-tab dashboard pattern: persistent top tabs Dashboard / Compare / Backup Progress / Settings, each with rich card layouts.

Why

The current single-screen flow is fine for a one-shot pull. The mockups envision DumpSock as a recurring tool: compare iPhone state against your destination, manage multiple devices, inspect job history. That needs more surface area than a single screen.

Scope

Tab bar: persistent in the title-bar area. Active state with red underline.
Dashboard: storage gauge (separate issue), connected-device card, big red "Dump it & back it up" CTA, last-backup summary.
Compare: side-by-side iPhone vs. destination. List photos present only on device, only on disk, in both. Bulk select + actions.
Backup Progress: the existing pulling screen, but with multi-job history below (when has the user backed up before).
Settings: output folder, advanced flags as toggles, telemetry-disabled badge, version + brand info.

Reference

`assets/mockups/playful_ui_design_for_dumpsock_v2.png` — desktop UI mock.

Acceptance

All four tabs render and switch cleanly.
Existing pull flow continues to work, now invoked from the Dashboard CTA.
Compare tab can read the destination index and produce the diff against a fresh AFC walk.
Settings persist via the existing `internal/gui/config.go` blob.

## S01E11 — *The Dashboard Era* Current GUI is a 5-screen state machine on one viewport. The v2 design system (see \`assets/mockups/playful_ui_design_for_dumpsock_v2.png\`) calls for a multi-tab dashboard pattern: persistent top tabs **Dashboard / Compare / Backup Progress / Settings**, each with rich card layouts. ## Why The current single-screen flow is fine for a one-shot pull. The mockups envision DumpSock as a recurring tool: compare iPhone state against your destination, manage multiple devices, inspect job history. That needs more surface area than a single screen. ## Scope - **Tab bar**: persistent in the title-bar area. Active state with red underline. - **Dashboard**: storage gauge (separate issue), connected-device card, big red \"Dump it & back it up\" CTA, last-backup summary. - **Compare**: side-by-side iPhone vs. destination. List photos present only on device, only on disk, in both. Bulk select + actions. - **Backup Progress**: the existing pulling screen, but with multi-job history below (when has the user backed up before). - **Settings**: output folder, advanced flags as toggles, telemetry-disabled badge, version + brand info. ## Reference \`assets/mockups/playful_ui_design_for_dumpsock_v2.png\` — desktop UI mock. ## Acceptance - All four tabs render and switch cleanly. - Existing pull flow continues to work, now invoked from the Dashboard CTA. - Compare tab can read the destination index and produce the diff against a fresh AFC walk. - Settings persist via the existing \`internal/gui/config.go\` blob.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

hartle-tech/dumpsock#2

No description provided.

Rows
Columns