Skip to main content
Review mode is built around one idea: pair a device once, then it just works natively from then on. There’s no separate reviewer app to install and no login screen to see every time — after the first pairing, the overlay is simply part of the app on that device.

​
Pair once per device

A teammate pairs their device to an app from the Tappify dashboard. Pairing is a single, explicit act — scanning a QR code or tapping an activation link — and it only has to happen once per device, per app (or once ever, if team-wide pairing is set up). See Activating devices for the walkthrough.

​
The overlay lives natively afterwards

Once paired, a small pill appears anchored to a screen edge whenever the app is open on that device — no relaunching a separate tool, no browser tab. Tapping it starts a new comment; long-pressing it opens the thread list for the current screen. See Commenting for how reviewers use it day to day. The overlay is inert unless a paired org member is present — it doesn’t exist on a device until that device has been through pairing, and it disappears again the moment a device is revoked or an app’s gating mode no longer allows it.

​
Comments are anchored to a screenshot, a screen, and a build

Every comment starts the same way: the current screen freezes to a screenshot, you drop a pin, and you write a comment. That thread permanently records the screen it was taken on and the exact app version and build number the app was running — so a thread from build 140 stays anchored to what build 140 looked like, even after build 142 changes that screen. See How review mode works above and Screen names for how screens get identified.

​
Activation flow

Everything after that first pairing — cold launches, backgrounding, foregrounding — is handled silently by the SDK. The reviewer never sees it happen.