> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tappify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Commenting

> Leaving and reading review comments from the in-app overlay — the pill, pins, mentions, threads, and offline behaviour.

Once a device is paired (see [Activating devices](/sdk/activating-devices)), a small
draggable pill appears anchored to a screen edge whenever the app is open. Everything below
happens without leaving the app.

## Leave a comment

<Steps>
  <Step title="Tap the pill">
    This captures the current screen and drops into pin mode over the captured image.
  </Step>

  <Step title="Drop a pin">
    Tap the spot your comment is about to place a pin there.
  </Step>

  <Step title="Optionally, mark a region">
    Tap **Crop** to drag a box around just the part of the screen you mean — the thumbnail
    becomes that region instead of the whole screen.
  </Step>

  <Step title="Write and submit">
    The composer opens. Type your comment — start typing `@` to mention a teammate — and
    submit. This uploads the screenshot and creates the thread in one action.
  </Step>
</Steps>

Your comment is now attached to that exact screen, on that exact build. If the screen
changes in a later build, the thread stays anchored to what it looked like when you
commented — see [How review mode works](/sdk/how-review-mode-works#comments-are-anchored-to-a-screenshot-a-screen-and-a-build).

<Note>
  **Offline?** Submitting with no connection queues the comment instead of failing — the
  pill shows how many are waiting. They post automatically, in order, the next time you're
  back online, and you'll get a confirmation. Nothing is lost and nothing double-posts.
</Note>

## Read threads for the current screen

Long-press the pill instead of tapping it to open the read flow: a thread list with a
**This screen** / **All** filter, plus an **Unread** and **@ You** filter. A dot marks
threads with something new; **@ You** narrows to threads where a teammate mentioned you.

On the screen you're currently viewing, open threads also show up as **live pins** right on
top of your app — tap one to open it. Pins from an older build are labelled so you know they
predate what you're looking at.

## Reply, resolve, and manage

Open a thread to see its full history. From there you can:

* **Reply** — posted the same way as the original comment.
* **Resolve / reopen** — toggle the thread's status; a resolved thread shows who closed it
  and on which build.
* **Edit** your own comment, or **delete** a thread you started.
* **Mute** a thread so it stops marking itself unread for you (doesn't affect teammates).
* **Copy link** — a shareable link that opens the thread in the dashboard.

Replies and status changes made from the dashboard show up here too, next time the thread
list refreshes — there's no realtime push, so give the app a background/foreground cycle (or
pull-to-refresh) if a teammate's reply doesn't appear immediately.

<Note>
  Screen names in the thread list come from the screen's identifier, which is
  auto-generated unless you've tagged it — see [Screen names](/sdk/screen-names) if you're
  seeing an unhelpful name like `HostingController` instead of something like `Checkout`.
</Note>

## Managing threads from the web

Everything you can do in-app — reading, replying, resolving, mentioning — is also available
from the dashboard, plus a build-and-screen-grouped overview across your whole team. See
[Dashboard Review tab](/sdk/dashboard-review-tab).