Skip to content

chore: compare two-line capability status markers and requirement pills - #754

Closed
sybohy wants to merge 3 commits into
mainfrom
prototype/devdb-two-line-status-iterations
Closed

sybohy wants to merge 3 commits into
mainfrom
prototype/devdb-two-line-status-iterations

Conversation

@sybohy

@sybohy sybohy commented Oct 28, 2026 •

Copy link
Copy Markdown
Member

Open the three-iteration comparison

1 · Current · 2 · Checks + info · 3 · Requirement pills

August with mixed check/info states · Nuki with requirement pills. The brand selector also includes KeyInCode. Switch with the bottom picker or keys 1–3; R resets expanded rows.

Two-line Supported Devices rows need a clear distinction between unconditional support and additional setup requirements while keeping capability names visible. This design preview compares three treatments on the same compact row:

  1. Current: the selected two-line layout with capability glyphs, retained unchanged as the baseline.
  2. Checks: green checkmarks for unconditional support, amber information icons for requirements, and neutral capability labels.
  3. Pills: the same check/info treatment, replacing the generic Requirements affordance with explicit Bridge Requirements, Keypad Required, and Subscription Required pills.

Pills are deduplicated per device and derive only from known canonical requirement messages. Unfamiliar requirements use Other Requirements; the full source copy and affected capabilities remain in the row disclosure. Models with no listed requirements do not receive pills. All three desktop summaries remain 89px (90px with divider). The pill variant wraps on phones to preserve complete labels.

Validation: typecheck, repository lint, and example build pass. Browser checks exercised all variants, Nuki/August/KeyInCode data, mixed check/info states, absent requirement pills for unconditional models, pill-click and keyboard expansion, canonical subscription/bridge/keypad text, model identifiers, filters/search/reset, reload persistence, reduced motion, light/dark themes, and 1200/760/390/320px layouts. No console errors or page overflow; API responses were 200 or normal 304 revalidation. Physical-phone and screen-reader review remain checks for the selected production treatment.

Isolated review page: /examples/supported-devices-prototypes. Production components and docs remain unchanged pending selection.

Design review: https://linear.app/seam/issue/DEVDB-466
Tracking: https://linear.app/seam/issue/DEVDB-469

Hosted browser verification and all CI checks pass.

Two-line option 2 — August check and info states

Two-line option 3 — Nuki requirement pills

Superseded by #755, which retains these three design treatments and adds the synced desktop/iPhone comparison. Current preview: https://react-etr7haqdj.seam.vc/examples/supported-devices-prototypes?v=3&compare=1

This branch was successfully deployed

1 active deployment
Preview — 302df5c8 Deployed Oct 28, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant