Product Organization & Desktop Experience
X Command Center
Private Desktop App
A local hub for tracking project progress, checking scheduled work, launching apps, and finding what needs attention.
Private Local App · Case Study
Key DecisionKeep one shared snapshot behind the desktop and browser views.
The Case Study
- Problem
- As personal projects grew, the context needed to resume work was scattered across folders, repositories, notes, and schedules. Finding what was unfinished or needed attention became a task of its own.
- What I Built
- A project hub that connects purpose, status, next steps, app launch, scheduled work, and history. A Windows desktop window and browser use the same local interface and service.
- How It Works
- A collector reads an explicit list of personal projects and builds one shared snapshot from project documentation, version-control metadata, site checks, and schedules. The desktop and browser views read that same snapshot. A local service handles refresh and recovery; reopening the installed app restores its existing window.
- Where It Stands
- Available as a local browser and Windows app with Start and Desktop launchers. The design establishes a consistent visual language across related tools while keeping project facts close to their source. The public case study uses a capability illustration instead of a real workspace screenshot.
- Evidence and Limits
- Testing the actual desktop launch action caught an outdated configuration reader that ordinary checks had missed. The callers now share one reader with regression coverage.
- The collector is deterministic and makes no AI calls. Status comes from project records, not an automatic assessment of productivity.
- Private project data, schedules, notes, and runtime snapshots are excluded from this case study.
- Product Stack
- Node.js · JavaScript · HTML and CSS · Electron · Local Service · Structured Project Metadata
- Evidence As Of
- 2026-10-27