evonx
Log in
All pages

Annotate the preview

Point at the exact element you mean - annotations become precise, contextual feedback for the AI.

"The button is in the wrong place" invites the question which button, and where should it be? Annotation mode removes the ambiguity: you mark elements directly on the running preview, write a note on each, and the AI receives feedback pinned to the exact parts of the UI you meant.

Annotating a preview

  1. Open your app in a preview and turn on annotation mode.

  2. Navigate to the screen you want to change — annotation works on the live app, so you can browse to any state first, including ones behind a few clicks.

  3. Click the element you mean. It's highlighted, and you attach a note: "this heading is too small", "move this next to the save button", "this price is wrong for members".

  4. Add as many annotations as the change needs, then send. Your notes — with their attachment to real elements — go to the AI as one request.

The result is feedback with coordinates: the AI knows precisely which component each comment targets, not a guess parsed from prose.

When to reach for it

  • Visual polish rounds — a handful of small corrections across one screen beats five separate chat messages.
  • Anything hard to name. Most app elements don't have names a non-developer would know; pointing beats describing.
  • Review before merging. Walking a thread's preview and annotating everything that's off is a natural way to compose your revision feedback for the pull request.

Last updated: September 4, 2026