Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01P5YBdwj33XByFVTvu9bfci
8.2 KiB
/gui — James-eye review
Ready: 8 Nov, held up next to /api and /agents (no score). Phone chapters now lead with their object (title and counter, then the object, then the words) instead of a squeezed two-column row, the compare's devices are sized to the window so they never reach the platform names, and chapters 01 and 03 move on their own (each platform lit in turn, the flat rule re-emitted); the review's fixes 1-9 hold (sheet at rest, picker field shows the value, small opened sidebar, platform-only opened copy, Get GUI on one line, chip and card hover). taste/unique/parity OK (text 70/70, links 2/2); 0 console errors from this page (only the shared footer hydration warning, which /agents shows too), no overflow/overlap at 1470x801 and 375x812. 8 Nov copy rule: copycheck missing 0 of 27.
7 Nov, round 5, walked at 1470x801, 375x812 and 320x640 (isMobile, hasTouch) with Playwright Chromium: frames at 0, 1 and 3 s with no input, wheel or touch scroll one screen at a time with 1.5 s dwell, hover and press on desktop, tap on phone, platform card opened and closed with Esc and with Back, overflow and art-to-text overlap measured, plus a prefers-reduced-motion load at desktop and phone. Every screenshot taken with caret: 'initial'.
Verdict: 6/10
First complaint: "On the phone it falls apart straight away. The next section's heading is jammed right under the GitHub button, then there's a big white gap, and the actual thing you're selling, the devices, is below the fold. And at small sizes the little 'Atomic CSS' label sits on top of the button inside the browser window."
The 11 answers
- Sells in 5 s, moves in 1 s? Desktop: yes. The h1 is followed by the YStack token strip, which cycles on its own ($4/$2/$4 to $6/$4/$8 within 1 s), and four drawn devices re-render the same card at once. That idea reads instantly. Phone: no. At 375x812 the stage h2 "Build it once. Ship it everywhere." starts 8 px below the "View on GitHub" button (button bottom 318, h2 top 326). After it comes a dead white band of about 190 px, and the strip only starts at y 542, so the devices sit below the fold. At 320x640 the strip starts at y 591 and the first screen holds only type.
- One in, one out? Mostly yes. The desktop pinned stage keeps the devices fixed while the chapter changes through 01 to 05: tokens restyle the card, the screens turn into code, dashed primitive outlines appear with a chip rail, then the card rounds and inverts. Chapter 06 hands off to the graphite shorthands room, where the token picker drives a live browser window. After that the page turns into a plain document: a code block, a card rail, a prompt, a band. On phone the stage chapters work, but each one is a stack of h2, h3, a paragraph, then the stage, so there is a lot of type before the object.
- A real object in every section? Yes: the stage, the token picker with its browser window, the terminal code block, four platform cards with device art, the agent prompt card and the band. Two weak ones. At rest the iOS card shows an empty phone with three grey skeleton bars; it only fills on hover, and there is no hover on touch. In the shorthands picker every row ends in an empty dashed box that looks like an unfinished placeholder.
- One ask, nothing floating, scale rhythm? On desktop the header ask changes from "Try Hanzo" to "View on GitHub" once the hero has gone, which is right. The hero has one solid ask, and the close pairs a solid button with a text link. Nothing floats over content on desktop. Scale has rhythm on desktop: h1 52, h2 26, close 44, and a 13 px mono caption. On phone the shared ask bar is fine. The h1 is 40 px over three lines and the stage h2 crashes into it, so the first phone screen is all type with no small-medium-big rhythm.
- Every hover and press answers? Token chips change ink and border, and the platform cards lift with a darker fill while "+" fills black. The opened card flies out of its card (shared panel style); Esc returns focus to the card and Back closes it without leaving the page. The active token chip ($4) shows no hover change. The card hover changes only the fill and the lift, with no detail added; the iOS card fills its screen, the others don't.
- Overlap, font swap, layout shift? No horizontal page overflow at any width. The code block and card rail scroll inside their own boxes. Overlap: at 320 the "Atomic CSS" stage chip covers the browser card's "Get started" button by 97x6 px, and at 375 it sits on the card's bottom edge. The phone hero/stage collision in point 1 is a layout fault. No console errors or hydration diffs on any load, including reduced motion. The h1 box did not move between 0, 1 and 3 s.
- Reference? apple.com product page: a pinned stage with the product held still while one panel changes. The motion is really there: scroll-scrubbed chapters with a 01 / 06 counter, plus an idle token cycle with Pause. A synchronized.studio card-open exists as a dialog that grows from the card. It is a dialog, not a page.
- Different from neighbours? Yes. The hero medium (one component rendered on four drawn devices) and the signature (tokens re-skinning every device at once) belong to this page.
- 18 parts? Mostly covered: hero, show-it stage, chapters, install, platforms, agent prompt, licence/stars proof, band; also states (copy, pause, reduced motion holding still) and mobile rail. Mobile hero composition (part 11) fails. Proof is thin: licence and "4 stars" only, but that is all Hanzo's page has.
- Banned tells? No hue, no gradient text, no eyebrow above a headline, no three equal boxes, no cursor glow, no fading buttons. The overlap at small phone sizes is on the banned list. The opened Desktop card scales its sidebar labels to about 24 px mono beside a 16 px card, so the art's own scale is broken.
- Copy untouched? Every heading, lede and label traces to
content/live/gui.jsonandcontent/pages/gui.html, and "Pause" and "Copy" are inui-strings.json. Three things are invented, all minor: the token values in the strip and picker ($2, $3, $6, $8, which are not in Hanzo's code), the "9:41" status-bar time, and the opened cards, which re-pair chapter body copy with platforms. iOS gets "One codebase" text and Desktop gets the "Design tokens / hostname" text, so the meaning of Hanzo's copy shifts.
Fixes, in order
- Phone hero. Give the hero its own bottom space (at least 44 px) before the stage. Do not let the stage's sticky h2 sit 8 px under the CTA, and remove the ~190 px void, so the token strip and both devices start inside the first 812 px at 375 and the first 640 px at 320. On phone the hero object has to be on the first screen.
- Stage chips at phone sizes. Move the "Atomic CSS" and "Native" chips below the device window, or out of the card's path, so they never overlap "Get started" at 320 (currently 97x6 px) or touch the card edge at 375. Re-measure at 320, 375 and 1470.
- Phone stage density. Before the stage, show only the chapter h3 and the 01 / 06 counter, and put the paragraph under the devices, or collapse it. The object should lead each chapter, not follow 4 to 5 lines of type.
- iOS platform card at rest. Show the "Hello, Hanzo" sheet in the resting art, as Android, Web and Desktop do. Touch has no hover, so on phone it is an empty phone.
- Shorthands picker. Drop the empty dashed slot at the end of each row, or give it a job (for example, the resolved value). As it stands it reads as an unfinished placeholder.
- Opened Desktop card. Keep the sidebar labels at the art's own scale (12-13 px mono, matching the closed card) instead of blowing them up to about 24 px beside a 16 px card.
- Opened card copy. Pair each platform with copy that is about that platform, or show only the platform name and its Hanzo sub-label. Hanging the "hostname brand" paragraph on Desktop and "One codebase" on iOS changes what Hanzo's copy means.
- Desktop "Get GUI". The h3 "Paste and ship" sits about 120 px above its own section h2 "Get GUI". Align them to one baseline, or put the h2 first, so the reading order follows the 8/5 split.
- Hover detail. Give the active token chip a hover state. On card hover, tell the visitor something (for example, the platform sub-label sliding up, or the token values the card uses) rather than only changing the fill.