Our 3-tab simplification (Docs, Kanban, Build) was a massive usability upgrade over our initial 5-tab dashboard. But as we and our early testers built complex applications with the agent, we hit a subtle yet frustrating ceiling: **The Tab Ping-Pong**.
To build a single feature, a developer was constantly flipping back and forth:
1. Open the **Docs tab** to review requirements and data models.
2. Switch to the **Kanban tab** to claim and track engineering tasks.
3. Switch to the **Build tab** to inspect the live preview and terminal logs.
4. Jump back to **Docs** the moment an API contract or screen layout changed.
Every tab switch broke the developer's flow state. Software engineering isn't a series of isolated linear pages—it is a deeply interconnected, multidimensional network. When specifications, task runways, database schemas, and running code live behind separate tabs, the developer (and the AI agent) has to maintain the entire architectural mental model in their head.
We realized that pruning tabs wasn't the final answer. We needed to eliminate tab boundaries entirely.
Key Lessons & Engineering Principles
- 1Tabbed interfaces create mental fragmentation by hiding architectural context behind page switches.
- 2Software engineering is relational, not page-based: specs, tasks, schemas, and code must be visible simultaneously.
- 3The ultimate developer workflow minimizes cognitive load by putting all lifecycle artifacts within direct sight.