GITHUB APPNO UX TEAM REQUIREDSTEP 1 YOUR URL

Tests passed.
They closed the tab.

Litmusly walks your live preview as a first-timer, a buyer, and someone on a phone — then leaves one GitHub comment with what they'd bounce on. Paste a URL. Work email next. Then Sam walks.

STEP 1 OF 2 · WORK EMAIL NEXT · THEN THE WALK

THEY JUST LANDED

SAM · FIRST-TIMER

0:00sam landed · 1440×900

0:09“Okay — what does this actually do?”

0:14“Charts, testimonials… where's the button?”

0:31“I'd probably just close this.”

0:48nav → /pricing · 280ms

1:08“The headline could be anyone's.”

2:12walk complete · 3 findings

WHAT THEY DID

closed the tab

WORKS WITHGITHUBVERCELSTAGEHANDONE GITHUB COMMENT · EDITS ITSELF · HARD-CAPPED SPEND

NOT UX REVIEWERS

These people don't work on your team. They land on the PR.

You already know how the page works. A first-timer, a buyer in a hurry, and someone on a phone don't. Litmusly walks the preview as them — before merge, not after the Slack thread.

VISITOR 01 / 07SAM

“I'd probably just close this.”

Clicked from Hacker News. Ninety seconds. Will close the tab.

THE TUESDAY THREAD

You didn't skip QA. You skipped being a stranger.

Unit tests catch what compiles. Pixel diffs catch what you can see. The person who lands from an ad, on a phone, and can't find the button lives in nobody's CI. So it ships. So you hear about it in Slack.

HOW

Open. Walk. Comment.

SEE A SAMPLE RUN ↗

01 · OPEN

Paste a URL. Or open a PR.

They land on the real preview — not a mock, not the Figma. Paste any public URL for a free walk. The GitHub App does the same on every pull request.

02 · WALK

They try the thing you think is obvious.

A first-timer from Hacker News. A buyer with four minutes. Someone on a phone, or a keyboard. If they can't find the button, that's the finding.

03 · COMMENT

One GitHub comment. Edits itself.

Blocker, friction, or nit, each with a quote from the walk. Force-push and it updates in place. Quiet when nothing's wrong.

DANA · FOUR MINUTES

She doesn't work here. She still has to buy.

Dana found you on LinkedIn. She has a meeting in four minutes. If she can't say what this is to her CTO, she leaves. That's not a UX nit. That's a lost eval — caught on the walk, not in a copy workshop.

DANA · BUYERWHAT SHE HITS

HEADLINEA competitor could run this line.

THE JOBThe problem she has is never named.

PROOF“Save time” — no number she can repeat.

RISKNothing answers “what if this doesn’t work.”

NEXT STEPThe button sells the click, not the outcome.

WHERE IT FITS

Not another test. A visitor in CI.

Keep the suite you have. This is the person who wasn't in the room when you shipped.

THE DIFF

THE PIXELS

THE VISIT

Logic bugs

✓

—

Pixel regressions

—

✓

—

Dead-end clicks

—

✓

Copy a buyer wouldn't use

—

✓

"Where do I click?"

—

✓

Runs on every PR

✓

THE SEVEN

Seven visitors. One comment on the PR.

Each one says what they'd actually do — and what they ignore. That's why the comment stays quiet.

Sam

“I'd probably just close this.”

Dana

“I can't explain this to my CTO in one sentence.”

Marcus

“If I have to pinch-zoom, we're done.”

Priya

“The button isn't in the tab order.”

Kofi

“I don't know what this actually does.”

Jordan

“I was here two weeks ago. Where did that setting go?”

Elena

“Where's the permissions list?”

START HERE

Paste a URL first. Install when you want it
on every PR.

Already shipping on Vercel? Connect GitHub →

Tests passed.They closed the tab.