- README.md: what this is, how to run and build it, the folder map, how light and dark mode work (@hanzo/appearance, @hanzo/design), where every price and checkout link lives, scripts, and known differences from live - docs/build-notes/: status files, request notes, per-page checklists and reviews, plans - Removed: screenshot galleries, captures of third-party sites used as references, the generated status page and its script, editor config, a personal working-rules file - Code comments point at the new docs paths (no code changes) Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01P5YBdwj33XByFVTvu9bfci
8.8 KiB
/chrome — James-eye review
Reviewed 2026-11-07 (round 4, independent critic), walked moving at 1470x801 and 375x812.
Verdict: 7.5/10 Ready: 8 Nov, held up next to /api and /affiliate (James's new bar, no score). The round-4 fixes held (phone CLS 0.000, window fits, one closing block, working policy pill); this pass keeps the rested window alive (CDP dot breathes, panel field and Paste prompt wait at a caret: 0 still screens at either width), cut the white bands around the surfaces sheet, fixed a reduced-motion hydration error on the hero window, and stopped capability rows jumping 24px. copycheck missing 0 of 82 (the step titles, Organization Site Policy and Agent overlay active now sit in plain text spans). taste/unique/parity OK (text 88/88, links 9/9); 0 console errors (also reduced motion), no overflow at 1470 and 375. Shared, not this page: headless Chrome here reports no (hover: hover), so motion.mjs flags every hover-media rule as dead (checked by hand: pills, asks and links answer).
First complaint: "On my phone the side panel jumps about while it runs, and the ask box bounces up and down. Then there's a whole screen that's just one sentence on white, and in the black room I type an address and can't see the answer without scrolling."
Proof: docs/build-notes/review/chrome/desktop-first.jpg, phone-first.jpg, desktop-walk.jpg (the text-only "Real-time browser intelligence" screen), phone-walk.jpg (the phone side panel after its run).
The 11 answers
- Sells in 5 seconds, moves within 1 second? Yes. The h1 (52px desktop, 40px phone) with its lede and one solid "Add to Chrome" sit beside a full-width Chrome window. Within a second the side panel ticks "Step 1/4", then 3/4 by about 4 s. On the phone the h1 runs 4 lines at 40px (the brief says 3), but the h1, lede, ask and the top of the window still fit the first screen.
- One in, one out? Mostly. The window, then the paste line, then three pinned chapters (01/02/03, one panel changing), then capability rows with a render that changes, the black governance room, the handoff rail and the close. Two parts read as a document. (a) The "Real-time browser intelligence under enterprise control" screen is only a heading, a lede and the "WHAT IT IS" caption, with roughly 150–250px of empty white above and below it at 1470x801. (b) After the handoff rail, the hairline rows "Looking for Firefox…" and then "Get Hanzo in Chrome / Deploy to Cloud" come one after another before the close.
- A real object in every section? Nearly every section has one: the window, the agent prompt card, the chapter renders (tabs checklist, MCP bridge, toggles), the capability render, the policy tester, the rail renders and the small "Allowed" frame in the close. The exception is the "Real-time browser intelligence" screen, which has no object.
- One ask, sticky after the hero? Yes. The hero has the solid "Add to Chrome" plus two text links. Once the hero is passed, the desktop header's solid button becomes "Add to Chrome", and the close repeats it once. Nothing floats over content. Scale has rhythm: h1 52, chapter heads 32, section heads 26, row titles 14–21, close 44, with no screen where everything is big. One problem: the black room's heading sits at y≈530 with about 300px of empty black above it.
- Every hover and press answers? Mostly. Primary: #0a0a0a → #262626 on hover, scale .98 on press, no jump. Pause: grey fill, scale .97, then becomes Replay. Inspector tabs: ink plus underline. Capability rows and rail stops open on hover and press .98. The "Hanzo Bot" pills fill ink. The tester chips brighten. Copy shows "Copied" for about 1 s, and the clipboard holds exactly the displayed prompt. One dead control: the hero window's "Allowlist / Allow all sites" segmented control in the Organization Site Policy card looks pressable but does nothing on hover, press or click (the same control in the black room works). Text links ("Configure Org Policies", "Deploy to Cloud") only nudge 1px on press; their colour and background don't change on hover.
- Overlap, font swap, layout shift? No overlap and no horizontal overflow at either size, and no console or page errors. No font swap was visible. Desktop CLS is 0.002. On the phone, CLS is 0.085 over 12 s when the window's side panel is in view. The step rows jump 40–48px as each result opens and the previous one collapses ("done" 448→400,
xch-res401→354), and the ask fieldxch-askbounces 605→627→605. This repeats at about 7.2 s, 9.6 s and 12.0 s and reproduced twice. The coverage card's claim that "results opening never move the page" is false on the phone. - Which reference, and is its motion there? Apple product page: the product is the hero, pinned chapters change one panel with a 01/02/03 index, and the sub-ask sits in the header. That motion is really there. Motion kinds are mixed: time (the self-running agent run), pointer (window tilt, renders that change on hover), state (inspector tabs, the policy pill, the tester verdict) and scroll (the pinned chapters, the rail walking). Scroll is not the majority.
- Different from its neighbours? Yes, though by a moderate margin. /extension uses a left heading with a stack of three browsers on the right. /chrome puts one full-width, inspector-led window under a split heading. Both still use a browser window as the hero medium.
- All 18 parts covered? The card has 18 of 18 filled. The claims hold on the page except two. Part 11 says opening results never moves the page, which is false on the phone (see 6). Part 3 says "one idea per 100svh", but the "What it is" screen holds a sentence and no object. Parity is true (
parity.py /chrome: text 88/88, links 9/9). - Banned tells? None of the major ones: no hue, no gradient text, no kicker over the h1 or any h2, no icon boxes, no cursor glow, no button that fades on hover. Minor: inside the window render, the mono line "ACTIVE TAB · STAGING.ACME.INC" and the "Agent overlay active" pill sit above the "Acme Pro Enterprise Checkout" h3. It is part of the product mock, but it reads as an eyebrow plus a pill above a heading.
- Copy untouched? Yes, parity 88/88 text and 9/9 links.
Fixes (ordered, most important first)
- Phone side panel layout shift (CLS 0.085). At 375x812, the step list in the window's side panel reflows each time a step's result opens and the previous one closes: rows move 40–48px, and the "Ask Hanzo…" field moves about 22px down and back. Give each step row a fixed height and let the result appear in a reserved slot (or animate it with transform/clip-path only), and pin the ask field to the bottom of the 516px panel so it never moves. Target CLS under 0.02 with the window in view for 15 s.
- Give the "Real-time browser intelligence under enterprise control" screen an object, or close it up. At 1470x801 it is a 32px heading, a lede and the "WHAT IT IS" caption floating in about 600px of white. Either join it to chapter 01, so the heading sits over the pinned stage as its title (the first panel arrives in the same viewport), or give it a small live object from text already on the page. Also cut the empty bands above "Paste and ship" and above "Built for engineering…" (about 200px of white each) so the next object peeks in.
- Black room fit. At 1470x801 the room's heading sits at y≈530 with about 300px of empty black above. The tester's "Allowed" verdict sits below the fold while you use the chips or the field, so you act and can't see the answer. Top-align the copy with the tester card, and fit the card (toggle, chips, field, chips, verdict) inside 801 − 60px, for example by putting the verdict beside the field or tightening the chip rows.
- Dead control in the hero window. The "Allowlist / Allow all sites" pill in the window's Organization Site Policy card looks pressable but does nothing. Either make it work like the black-room toggle (switching the "Allowed:" line), or render it as plain text so it doesn't promise a press.
- Tidy the tail before the close. The rail is followed by two hairline blocks ("Looking for Firefox, Safari…" with four pills, then "Get Hanzo in Chrome" with one "Deploy to Cloud" link), and then "Put Hanzo in every tab". That is three endings in a row. Keep the copy but make them one block: put "Get Hanzo in Chrome · Deploy to Cloud" as a single line under the pills, not a second h3 row with its own hairlines. This also lets the close arrive one screen sooner.
- Smaller: text links ("Configure Org Policies", "Browser docs", "Deploy to Cloud", "Manage Chrome Policies") should show something on hover: an underline drawing in, or the arrow sliding about 4px. On the phone, let the h1 break into 3 lines at 40px, as the brief asks (balance or a tighter measure). Inside the window render, consider moving "ACTIVE TAB · STAGING.ACME.INC" and the "Agent overlay active" pill below the "Acme Pro Enterprise Checkout" title, so the mock doesn't model a kicker over a heading.