Try That UI

About

A place to judge the UI change before anyone edits the code

Try That UI is a review workspace. You bring a real screen, keep that Current state intact, and put a Proposed change beside it so the decision is about the difference, not a fresh mockup with no baseline.

What it is

The product starts from something you already have: a public URL, a screenshot, or a connected source. That reference stays visible. Proposed is where a scoped change can be stacked on top, including an isolated component prototype when you want to try an interaction in the review itself.

A captured screen is a visual reference. It does not replay your application's behavior, and it does not edit your repository. The prototype is for the review. Building and testing the real change still happens in your own code. When the review is done, you keep the direction, reject it, or share a decision record that carries the scope, the preview, and the next step.

Optional repository connections use the permissions shown on that provider's consent screen. Try That UI does not write, merge, or deploy a connected repository unless that separate approval is given in the product. The how it works page walks through the same loop in order.

Who it is for

It is for the person who has to decide whether a UI change is worth making. That includes developers, design engineers, product designers, product managers, technical founders, and both small teams and larger product teams. You can start alone. When someone else needs to judge the same change, they look at the same Current and Proposed comparison instead of a thread of detached screenshots.

Two situations come up often. One is a product design review, where product, design, and engineering need one object to align on before implementation. The other is an AI-generated UI review, where a proposal appeared quickly and the remaining question is whether it is faithful to the product you already ship.

How a review moves

  1. Add a reference. Paste the interface, screenshot, or source you want to improve.
  2. Scope the proposal so Current and Proposed stay comparable. One change should be legible.
  3. Try an isolated component prototype on Proposed when the interaction is the question. Your source app stays unchanged.
  4. Keep, reject, or share the decision, with the evidence attached for the handoff.

If all you need is a note on a single frame, a screenshot comment is enough. The screenshot comparison explains when that stops being sufficient. The public pattern library is a separate, small set of review notes, starting with reversible actions.

Who built it

Try That UI is built by Mike Yerke. Signup is open. Create a free account with your email, 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 is required.

Questions about the product, privacy, or these pages can go to hello@trythatui.com.

Questions

Does Try That UI change production code?

No. Current stays intact while you compare a proposal and try isolated component prototypes. Implementation and testing happen in your own code. A connected repository is not written, merged, or deployed without a separate approval.

Is Try That UI publicly available?

Yes. 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.

Who built Try That UI?

Try That UI is built by Mike Yerke.

Create a free account