UI decisions you can actually review

See the better UI before anyone changes the code.Review better UI before the code changes.

Bring a real screen, URL, screenshot, or connected source. TryThatUI keeps Current intact while you stack multiple grounded changes on Proposed, then compare, test, share, and hand off the decision.

Preparing signup protection…We do not sell your address. PrivacyAlready have access? Sign in →
Private early access.Invite-only · no card required.For anyone making a UI decision.
Product previewIllustrative
First review

Review the decision

Current screen preserved
Meaningful elementPrimary checkout actionGrounded in the supplied screen · changes stay scoped
A
Make it easier to scanTighter label rhythm
B
Strengthen hierarchyClearer primary action
C
Reduce visual weightQuieter supporting detail
KeepRejectShare
Browse the library and stack changes before you decide what to keep.
See the capture flow before you sign in

Start from a real surface.

A reference can be a link, screenshot, or repository surface. This short preview shows the handoff; the real capture happens inside the app.

Preview the handoffThis preview does not fetch, store, or send the address. Open the app for the real capture flow.Sign in to capture
your-site.com
Nothing captured yet.
Built forDevelopersDesign engineersProduct designersProduct managersTechnical foundersSmall teamsProduct teams
The output PMs can carry forward

Make the decision portable.

A review should leave behind more than a screenshot. TryThatUI assembles the scope, reason, behavior, and next step into one honest record that design, product, and engineering can share.

Example record · illustrative only · no invented customer metrics.

Decision record / CheckoutPrimary action review
Assembling evidence
ScopeCheckout · primary action
ReasonGive customers a reversible review step
Evidence3 interactions · Current versus Proposed
DecisionReady for product + engineering review
Collecting 0/4 signals
From reference to decision

A grounded review in four moves.

Enough structure to make the decision clear. No process theater.

01

Reference

Paste the interface, screenshot, or source you want to improve.

02

Proposal

Scope the change so Current and Proposed stay comparable.

03

Behavior

Replay what happens after the click - not just how it looks.

04

Evidence

Keep the reason, impact, and reversible path with the decision.

The whole product, in one drag

Drag it. That’s the review.

One element changed - the primary action. Everything else is identical, which is the point: you are looking at a difference, not two screenshots.

Paper & InkShopOrdersHelpCart · 2
Review your orderTwo items · delivered Thursday
Field notebookIn stock£18.00
Ink refillShips Thursday£6.00
Subtotal£24.00
Total£24.00
Place orderLater
Paper & InkShopOrdersHelpCart · 2
Review your orderTwo items · delivered Thursday
Field notebookIn stock£18.00
Ink refillShips Thursday£6.00
Subtotal£24.00
Total£24.00
Place orderLater
CurrentProposed
50% proposedDrag, or use the arrow keys

The proposal is scoped to one element, and reversible.

Elementbutton.primary
Changedpadding, radius, size, color
Untouchedorder details and total
Revertone click
Same action, both versions, at the same time

Most changes aren’t a bigger button.

They’re what happens after you click. Pick an interaction and run it - the same three actions replay on Current and Proposed together, so you are comparing behavior instead of screenshots.

Paper & InkCurrent
Field notebook£18.00
Ink refill£6.00
Modal confirm · blocks the page
Remove item
Paper & InkProposed
Field notebook£18.00
Ink refill£6.00
Inline undo · reversible for 5s
Remove item
A blocking modal, or a reversible action with undo.
patternconfirm-modal → inline-undo
undo window5s
blockingtrue → false
elements touched1
Bound to one element, reversible, and exported with the capture that produced it.
Whole surfaces, not single elements

The hard ones are structural.

A table, a form, a menu - the changes worth arguing about restructure a whole surface. Both sides are live here: sort the table, walk the steps, type in the palette.

Sort Proposed by spend

Current
NameOwnerStatusSpendDate
Checkout · primary actionMikeyApproved$12820 Aug
Pricing card densityAnaIn review$6419 Aug
Nav label copySamReverted$1217 Aug
Empty state instructionAnaApproved$24014 Aug
Proposed
Status
Checkout · primary action
Mikey · 20 Aug
$128Approved
Empty state instruction
Ana · 14 Aug
$240Approved
Nav label copy
Sam · 17 Aug
$12Reverted
Pricing card density
Ana · 19 Aug
$64In review
Every column at equal weight, or the two people actually scan.Avoid when a simple list reads better than a grid.
What you get

Less debate. More confidence.

Decide faster

Put the actual difference in front of people before the meeting expands around it.

Catch the hidden UX

Review loading, failure, validation, undo, and modal behavior - not only the resting screen.

Keep changes bounded

Make one proposal legible without turning the rest of the product into collateral damage.

Hand off the why

Keep evidence attached so builders know what changed and reviewers know why.

“The hard part is not making another version. It is making the difference easy to judge.”
Built from the review pain

A practical tool for the people who make product decisions.

TryThatUI is built for the moment between “I think this could be better” and “let’s change the code.” It gives individual builders and teams the same shared object: the proposal, the behavior, and the evidence.

Private early access · opening in waves

Request a place in the next invite wave.

TryThatUI has not launched publicly yet. The product stays invite-only while we finish the workflow and verify it with a small group. Join the waitlist now; if approved, you will receive one email when your access is ready. No card required.

Request early access
Questions, answered

Before you join.

Is this only for teams?

No. TryThatUI works for individual developers, product managers, design engineers, product designers, technical founders, small teams, and larger product teams. Start alone, then share the same evidence when more people join the decision.

Does it change production code?

Not during review. Proposals stay bounded and reversible, so you can compare the behavior and evidence before deciding what should ship.

What can I use as a reference?

Start with a public URL, screenshot, or product reference. TryThatUI turns that input into a focused Current versus Proposed review rather than a disconnected mood board.

How does private early access work?

Request access with your email. We are inviting people in small waves while the product is unfinished; approved people receive one invite email when their cohort opens. Early access is free and does not require a card.

Your next UI decision can be clearer

Show the difference. Prove the behavior. Ship with confidence.

Preparing signup protection…We do not sell your address. PrivacyAlready have access? Sign in →