UI decisions you can actually review

See the better UI before anyone changes the code.

Bring a real screen, URL, screenshot, or connected source. Try That UI keeps your Current screen as it is and lets you layer changes onto a separate Proposed version. Try component prototypes, then share or export the decision.

Free account. A protection check runs before anything is sent. No card required.We do not sell your address. PrivacyAlready have an account? Sign in →
Free during beta.Open signup · 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.
Try a page before you create an account

Start from a real surface.

Paste a public page and see it next to 3 proposed versions in a few seconds. No account needed for your first 3 tries a day.

Scripts are stripped and every version opens in a locked frame. Nothing is saved.
your-site.com
CurrentProposeddesktop · 390px
This picture is the layout, not a capture. Your page shows up on the next screen.
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. Try That UI assembles the scope, decisions, preview changes, and next step into one 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
EvidenceCaptured screen · proposed changes
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, with no extra steps.

01

Reference

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

02

Proposal

Scope the change so Current and Proposed stay comparable.

03

Prototype

Try isolated component interactions on Proposed. Your source app stays unchanged.

04

Evidence

Keep the decision, preview details, and next steps together for handoff.

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
Built-in behavior examples

Most changes aren’t a bigger button.

Pick a built-in scenario to compare three preset actions on Current and Proposed. In the app, you can try isolated component prototypes; captured screens do not replay your app’s behavior.

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
Preset example only. Source application behavior still needs testing after implementation.
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.

Try an interaction

Explore component prototypes before implementing and testing behavior in your own app.

Keep changes bounded

Make one change easy to review without disturbing the rest of your product.

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.

Try That UI 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 decision, and the evidence.

Free during beta

Create an account and start a review.

Try That UI is open. Create a free account, or paste a public URL and open Current versus Proposed before you sign in. Saving a decision record asks you to sign in. No card required.

Create a free account
Questions, answered

Before you join.

Is this only for teams?

No. Try That UI 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?

No. Current stays intact while you compare visual proposals and try isolated component prototypes on Proposed. Captured screens do not replay your application’s behavior; implementation and testing happen in your own code.

What can I use as a reference?

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

How do I create an account?

Create a free account with your email. No invite code and no card. You can paste a public URL and open Current versus Proposed before you sign in. Saving a decision record asks you to sign in.

Your next UI decision can be clearer

Show the difference. Record the decision. Hand off with clarity.

Free account. A protection check runs before anything is sent. No card required.We do not sell your address. PrivacyAlready have an account? Sign in →