TechnicalCollectible prompt
Feature comparison table that works on a phone
Act as a senior designer and front-end engineer. Build a comparison table for {{business_name}} covering {{features}}, compared with the alternative at {{competitor_url}} (or between our own options if I say so). Reuse the existing table components.
Honesty:
- every competitor cell comes from their public pages, with a "checked on" date and a link
- include rows where they win; leave out anything you can't verify, and tell me
- no "Partial" without a footnote saying what's partial
Semantics: a real table with a caption, column headers with scope, and row group headings (a th spanning the row) for feature areas. Checks and dashes are icons with visually hidden text ("Included", "Not included"); limits are text ("Up to 5 users").
Layout:
- 1280: all columns, sticky header row, the first column 30% wide with left-aligned labels; values centered for icons, right-aligned for numbers in tabular-nums
- 768: same, sticky first column if it scrolls sideways
- 360: don't squeeze five columns. Show two at a time with a pair of selects ("Compare X with Y"), keep the first column, and keep the row groups as collapsible disclosures
The recommended column gets a 2px accent border and a label, not a glow.
States: focus-visible rings on the selects and disclosures; hover highlights the row on desktop; row help text in a footnote or a disclosure button, never hover-only tooltips; long feature names wrap; an empty group is hidden.
Type: column names 16 to 18px weight 600; cells 15px; group headings 13px uppercase with 0.06em tracking, at full contrast.
Motion: none beyond 150ms hover color; nothing under prefers-reduced-motion.
Avoid: checkmarks in our column for everything, red X icons shouting at competitors, a table you can only read by pinching, comparisons with no date.
End with the list of claims I need to verify before publishing.
Technicalnvoka.com/library/nvoka-feature-comparison-table-that-works-on-a-phoneScan to open
Technical
Feature comparison table that works on a phone
Compare options or alternatives in a real table that stays honest and readable at 360px.
Curated by Nvoka
v0LovableCursorClaude Code
Make it yours
Fill in the blanks and change any word. Only your copy changes, never the card.
Fill in the blanks
0 of 3 filledYour prompt
Act as a senior designer and front-end engineer. Build a comparison table for {{business_name}} covering {{features}}, compared with the alternative at {{competitor_url}} (or between our own options if I say so). Reuse the existing table components.
Honesty:
- every competitor cell comes from their public pages, with a "checked on" date and a link
- include rows where they win; leave out anything you can't verify, and tell me
- no "Partial" without a footnote saying what's partial
Semantics: a real table with a caption, column headers with scope, and row group headings (a th spanning the row) for feature areas. Checks and dashes are icons with visually hidden text ("Included", "Not included"); limits are text ("Up to 5 users").
Layout:
- 1280: all columns, sticky header row, the first column 30% wide with left-aligned labels; values centered for icons, right-aligned for numbers in tabular-nums
- 768: same, sticky first column if it scrolls sideways
- 360: don't squeeze five columns. Show two at a time with a pair of selects ("Compare X with Y"), keep the first column, and keep the row groups as collapsible disclosures
The recommended column gets a 2px accent border and a label, not a glow.
States: focus-visible rings on the selects and disclosures; hover highlights the row on desktop; row help text in a footnote or a disclosure button, never hover-only tooltips; long feature names wrap; an empty group is hidden.
Type: column names 16 to 18px weight 600; cells 15px; group headings 13px uppercase with 0.06em tracking, at full contrast.
Motion: none beyond 150ms hover color; nothing under prefers-reduced-motion.
Avoid: checkmarks in our column for everything, red X icons shouting at competitors, a table you can only read by pinching, comparisons with no date.
End with the list of claims I need to verify before publishing.