Lyba Nativ

Lyba Nativ brings Lyba's review loop to native apps: your client pins feedback inside a preview build of your app, your studio works through it in the Lyba dashboard, and the approval records the exact build that was signed off.

How native review works

On the web, every review round is a URL. In an app, every round is a build. Lyba Nativ works on preview builds of React Native apps, with Expo as the first supported setup.

1. You add the Lyba Nativ SDK to your app's preview builds.
2. Your client installs the preview build for the round.
3. Your client connects to the review by pasting the review link your studio sent them.
4. They tap Pin feedback on this screen, tap the spot, and write their comment.
5. The comment lands in your Lyba dashboard like any other comment, where your team triages it, resolves it, and requests approval.

Pins belong to screens and to your app

A pin in an app is tied to the screen it was placed on: the app route, such as /bookings/abc, rather than a web address. Reviewers can drop a point pin, attach a pin to an element, or drag a rectangle over an area, then reply and discuss just as they would on the web.

Each Lyba Nativ project holds your app's IDs, for example the iOS bundle ID and the Android package name. Lyba only accepts pins from an app whose ID belongs to the project, the same protection the web version gets by matching the site's domain.

Pins also carry the device and build they came from, and can include a screenshot of the screen, because an app screen (its scroll position, form contents or the record on screen) often can't be reproduced later.

Recorded review takes

A reviewer can review inside one continuous recorded take. The take captures:

• the screen,
• the reviewer's voice,
• a draggable on-screen face bubble.

Every pin and reply is stamped with its moment in the take. In the dashboard, your studio watches the take with the pins as markers on the timeline, and can jump to the moment each pin was placed.

Recording is offered, never forced

• Your studio decides per project. Recorded reviews are switched on or off per project with the Recorded reviews switch in the dashboard. Only studio owners and admins can change it.
• Your client decides every time. Before a take starts, the reviewer sees Record this review? with what is captured, who sees it and how long it's kept. They can choose Start recorded review or Review without recording. Pins work either way.
• The reviewer stays in control during the take. They can pause the recording, turn the face-bubble camera off, or discard the take.

Privacy during a take

• Private screens, such as identity checks, are never recorded. Studios can list those screens so that recording pauses on them and the camera is released, and can mask individual views in recordings and screenshots.
• Recording only covers your app. It pauses when the reviewer leaves the app.
• Only the studio that sent the review can watch the recording.
• Reviewers are asked not to read out card or bank numbers.

Approvals name the exact build

Approval works the same way as on the web: once every comment is resolved, your studio requests approval and the client signs off. The approval record names the build under review (platform, app version and build number), so there's never any doubt about which build was approved. Approval records never include recordings or screenshots.

Nothing ships in your store builds

The SDK is compiled out of store builds, not just switched off. A store build of your app carries no Lyba code at all, so your production users are never affected.

How long recordings are kept

A recording is deleted 30 days after its round is approved or archived. A take the reviewer discards is deleted immediately, and no recording is kept longer than 90 days after it was made.