Epic / tracking issue. Not for implementation yet — tracks the planned second consumer of `quadraui` that validates the extraction and proves the library works outside vimcode.
Background
Per `docs/UI_CRATE_DESIGN.md`, Phase D (month 5) calls for "one small example app as a second consumer to prove extraction." A k8s dashboard is an unusually strong fit:
- Lens is non-free (post-OpenLens fork), Electron-heavy
- k9s is excellent but terminal-only
- Nobody ships a cross-platform GUI + TUI k8s client from a single codebase. That's genuinely differentiating
The same binary running in TUI (SSH-into-bastion, prod kubeconfig context) and GUI (daily desktop work) with identical keybindings is a real value proposition neither existing tool can match.
Why this is the right validation app
It stress-tests almost every v1 primitive:
| Primitive |
Use in k8s app |
| `TreeTable` (#139) |
Namespace → kind → resources with status/age/restarts columns |
| `TextEditor` |
YAML editing with `kubectl apply` integration (validates `BufferView` extraction) |
| `Terminal` |
`kubectl exec` into pods — exercises Terminal beyond vimcode |
| Live-append text (#144) |
`kubectl logs -f` at real volume |
| `Palette` |
Cluster / namespace / resource switcher |
| `DataTable` |
Resource lists with sort/filter (or `TreeTable` with depth 0) |
| `Form` |
Port-forward dialogs, resource creation wizards, credential setup |
| `Dialog` |
Apply/delete confirmations with diff preview |
| `Spinner` / `ProgressBar` (#142) |
Long-running operations (rollout, drain, cordon) |
Priority impact on v1 scope
Because this app validates v1, several issues currently in the backlog should move to v1 must-have:
Confirmed before filing this epic.
Scope / approach
- Start after quadraui 1.0 publishes (Phase D per design doc)
- Separate repo, separate release cadence from vimcode + quadraui
- MVP: list/view pods across clusters, exec, logs, YAML edit, apply/delete
- Stretch: custom resources, Helm management, multi-cluster federation, RBAC browser, events stream
Success criteria
- Cross-platform binary (Win, Linux, TUI; macOS once quadraui 1.1 ships)
- Keyboard-first like k9s; mouse-supported like Lens
- Feature parity with k9s common workflows
- Competitive with Lens for visual presentation and ease-of-use
Dependencies
Non-goals for this issue
- Building any of this before quadraui extracts
- Competing with Lens on enterprise features (SSO, teams, audit) in v1
Epic / tracking issue. Not for implementation yet — tracks the planned second consumer of `quadraui` that validates the extraction and proves the library works outside vimcode.
Background
Per `docs/UI_CRATE_DESIGN.md`, Phase D (month 5) calls for "one small example app as a second consumer to prove extraction." A k8s dashboard is an unusually strong fit:
The same binary running in TUI (SSH-into-bastion, prod kubeconfig context) and GUI (daily desktop work) with identical keybindings is a real value proposition neither existing tool can match.
Why this is the right validation app
It stress-tests almost every v1 primitive:
Priority impact on v1 scope
Because this app validates v1, several issues currently in the backlog should move to v1 must-have:
Confirmed before filing this epic.
Scope / approach
Success criteria
Dependencies
Non-goals for this issue