Comparison
Screenshot feedback shows a frame. A UI decision review shows the change.
A screenshot is a good place to mark a visual note. It is a weak place to decide whether a product interaction should change, because the current state, the proposal, and the decision usually end up in different tools.
What screenshot feedback is good at
Pin a comment to a frame when the question is local: this label wraps, this icon is the wrong one, this spacing is tighter than the screen beside it. The artifact is one image. People who already share the context can resolve it quickly. You do not need a review workspace for that, and Try That UI does not ask you to stop doing it.
The same thread gets thin when the frame is not the current product, or when several things moved and nobody wrote down which one was accepted. A comment on an isolated mock can approve a screen the app does not have. Weeks later the implementation guesses which notes were the decision.
What a current-versus-proposed review keeps together
Try That UI starts from a URL, screenshot, or other reference and leaves that Current screen intact. Proposed holds the change you want judged, scoped so the two states can be compared. If the question is an interaction, you can try an isolated component prototype on Proposed. That prototype is not a replay of your application, and accepting it does not edit your repository.
The thing you share is the decision record: the scope, the preview of the change, and the next step. Keep, reject, or hand it to the people who will implement it. The how it works page is the sequence. The product design review is the same object used by product, design, and engineering together.
Choose from the decision, not from the tool
- Use a screenshot comment when one frame and a narrow note are the whole decision.
- Use a current-versus-proposed review when you need the baseline to stay visible, when more than one person has to agree, or when the handoff has to say what changed and why.
- Do not treat two unrelated mockups as a comparison. If neither side is the interface you ship, you are reviewing a concept, not a change.
A generated proposal is a common way to end up with a frame that has no baseline. Hold it against the current product using the AI-generated UI review, instead of commenting on the generation as if it were already the product.
Questions
Should I stop using screenshot comments?
No. Use a screenshot comment for a narrow visual note on a single frame. Use a current-versus-proposed review when you need the baseline, the change, and a decision that can be shared before implementation.
What does a Try That UI review add beyond the image?
It keeps the current screen intact, puts a scoped proposal beside it, and can hold an isolated component prototype. The output is a decision record. The capture does not replay your application, and the review does not change your code.
Is a side-by-side mockup the same thing?
Only if one side is the actual current interface and the other is a scoped change to it. Two unrelated compositions do not show what would change in the product.
Create a free account