Fact 120
In Mercury thread C-198 on June 29, 2023, Marcus endorsed the neutral warning circle, rejected the broken-link icon as vendor-specific and too narrow, and said the retry arrow should be used only as an action affordance rather than the main state icon.
Source evidence (1)
000624Jun 30, 2023 / 11:06 UTC-07:00
The latest activation-surface comments are below. Figma comment export File: Mercury activation surface v0.2 Page: Activation states / v0.2 Exported: 2023-06-30 09:26 PT Thread C-184 Frame: Invited member waiting on admin / first source — setup guide card Status: Open Jun 29, 2023 3:08 PM — Priya Last copy pass here. Current body text feels stiff. Proposed supporting line: “Use the setup guide to connect the first source and get the workspace ready.” CTA stays “View setup guide.” No new action. Jun 29, 2023 3:18 PM — Marcus Release-wise this is fine. Copy polish only as long as the locked CTA stays “View setup guide” and we don’t add a second button or alternate route. Jun 29, 2023 3:24 PM — Priya Yep, single CTA only. This is just a wording cleanup. Thread C-191 Frame: Preview card — 320 px / 360 px width study Status: Open Jun 29, 2023 4:02 PM — Priya Attaching small-width screenshots. At 320 px the preview card feels pinched: title gets too close to the edge and the body wrap is awkward. Proposed tweak is +8 px horizontal padding and a little more space above the footer. Not calling this blocking if text isn’t clipping. Attachments: - preview-card-320-tight.png - preview-card-360-tight.png Jun 29, 2023 4:17 PM — Marcus I checked current build on the narrow breakpoint. It wraps, but I’m not seeing clipping, overlap, or tap-target issues. Looks rough, agreed, but this feels like polish rather than a ship blocker unless QA finds truncation. Jun 29, 2023 4:23 PM — Priya Makes sense. If it stays readable, we can bucket it after blocker pass. Thread C-198 Frame: Sync failed state — icon options Status: Open Jun 29, 2023 5:11 PM — Priya Failed-state icon pass: A) neutral warning circle B) broken link C) retry arrow I prefer A. It reads cleanest across auth / permissions, source unavailable / timeout, and unknown / retry without implying one specific cause. Jun 29, 2023 5:24 PM — Marcus +1 against broken link. It makes the failure feel vendor-specific and too narrow. Warning circle is safest. Retry arrow is okay as an action affordance, not as the main state icon. Jun 29, 2023 5:32 PM — Priya Got it. I’ll keep the primary icon neutral and let the copy carry the bucket distinction. Thread C-207 Frame: Sample data preview mode Status: Open Jun 30, 2023 8:47 AM — Priya Possible line for sample-data preview mode: “Preview the workspace with sample data while your first source finishes connecting.” Intent is to make the surface feel less dead during queued setup. Jun 30, 2023 8:55 AM — Marcus This is the only one I’m nervous about. “Preview the workspace” reads close to a live / activated state if someone skims it. If sample data exists here at all, it needs to look clearly separate and preview-only, not like the real connected path. Jun 30, 2023 9:03 AM — Priya Fair. I can push it into a clearly labeled preview treatment and strip any success-looking styling. Goal is just to avoid a blank screen, not to imply the account is actually set up. Jun 30, 2023 9:12 AM — Marcus That works from my side if it stays visually partitioned and nothing about it can be mistaken for activation completion. Draft me a pasteable response I can put in the design file myself. I want it to separate the non-blocking polish that can merge or follow after the blocker pass from anything that makes sample data look like real activation. Keep Priya’s product ownership and Marcus’s release-readiness concerns in one lane, not another side debate.
Message 000624 in history