ADR-008: UX Strategy — Modern Default + Power Opt-In
Status: Accepted Date: 2026-03-16
Context
PSSaaS serves two distinct user populations with opposing UX preferences. New customers want clean, guided interfaces with progressive disclosure. Migrating customers (desktop app veterans) want dense, keyboard-driven interfaces where everything is visible at once — the way they've worked for years or decades.
Building two separate frontends would double maintenance cost. Building only a dense interface would repel new customers. Building only a clean interface would frustrate power users.
Decision
One frontend with two presentation modes. Same React components underneath, different layout and disclosure rules.
| Mode | Audience | Default? | Characteristics |
|---|---|---|---|
| Modern | New customers | Yes (default) | Dashboards, wizards, guided flows, progressive disclosure, card-based layouts |
| Power | Migrating customers | No (opt-in) | Dense grids, all fields visible, keyboard shortcuts, minimal whitespace, tab-driven navigation |
User preference controls which mode is active. The setting persists per user account.
Consequences
Positive:
- One codebase: Same React components, same API calls, same business logic. Only presentation varies.
- User choice: Each user picks the mode that matches their workflow preference
- Gradual migration: Desktop users can start in power mode and gradually explore modern features
- No dead-end UI: Power mode isn't a "legacy" mode — it's a legitimate interaction style for high-volume users
Negative:
- More frontend work: Components must support two layout modes. CSS, responsive behavior, and keyboard handling differ per mode.
- Testing surface doubles: Both modes must be tested for every feature
- Design complexity: UX designers must think in two paradigms for every screen
- Risk of power mode becoming "the real app" if migrating customers dominate early adoption