TryThatUI

How it works

From UI reference to a decision your team can use

TryThatUI separates deciding from implementing. It gives reviewers a grounded comparison first, then carries the approved decision forward.

1. Add a source

Start with a visual reference or a supported public repository. The source remains evidence for the proposal rather than becoming a vague prompt.

2. Compare current and proposed UI

Inspect both states, replay the interactions that matter, and see what changed. The goal is reviewable evidence, not a polished screenshot with no behavioral context.

3. Make a reversible decision

Approve the direction, request changes, or discard it. The resulting record gives product, design, and engineering the same handoff.

Request early access