How it works
From a real screen to a decision you can hand off
Try That UI is the review before the code change. Current stays as you captured it. Proposed is where a scoped change, and an isolated component prototype, can be judged. The output is a decision record, not an automatic edit.
1. Add a reference
Start with a public URL, a screenshot, or a product reference. That screen is the evidence for the review. It is not replaced by a prompt, and it is not redrawn as an unrelated mock. If you later connect a repository, the connection uses only the permissions shown on that provider's consent screen.
GitHub and GitLab are the repository connections described in the product privacy policy. Read access can list repositories and inspect the revision you choose. Write, pull request, merge, and deploy stay separate, and they do not run unless that approval is shown and given.
2. Keep Current and Proposed comparable
Current remains intact. You scope the change so a reviewer can see what moved and what did not. A useful proposal is one difference, not a redesigned product with no way to tell which part was the decision.
A captured screen is a picture of the interface you supplied. It does not replay your application's behavior. Trying a component on Proposed does not execute your production code or change the source you captured.
3. Try the interaction in isolation
On Proposed, you can try an isolated component prototype against the screen you brought in. That is how you look at a different control, an empty state, or an undo treatment without implementing it first. The prototype is review material. The real interaction is still built and tested in your own app, after you decide it is worth building.
4. Record a reversible decision
Keep the direction, reject it, or share it. The record is meant to carry the scope, the preview of the change, and the next step to design, product, and engineering. Sharing the record does not ship the change. Nothing is written, merged, or deployed to a connected repository unless that separate approval happens in the product.
What this review is not
- It is not a generator that lands UI in production by itself.
- It is not a replay of your live application. Captured screens stay visual references.
- It is not a substitute for a narrow visual note. Use a screenshot comment when that is all the decision needs. Use this loop when behavior, scope, or a handoff is the question. The screenshot comparison draws that line.
- Signup is open and free during beta. No invite code and no card. A pasted URL opens Current versus Proposed before you sign in. Saving a decision record asks you to sign in.
The about page says who the workspace is for. The reversible actions note is the first public pattern for reviewing recovery, not a claim that every product action is undoable.
Questions
Does Try That UI change my code?
No. The review can end in a shared decision. Implementation stays in your codebase. A connected repository is not written, merged, or deployed without the separate approval that operation requires.
Will a capture replay my app?
No. Captured screens do not replay your application's behavior. Use them to judge the interface you supplied, and use an isolated prototype when you want to try a component in the review.
Who is the workflow for?
Developers, design engineers, product designers, product managers, technical founders, and product teams. One person can run it. The same comparison is what you share when more people need to judge the change.
Create a free account