Ovo Logger · the screens

The tour, screen by screen.

Every frame on this page will come from one real study - a researcher, a participant, and a checkout flow with real problems - captured with the product doing its actual job. Nothing staged, nothing mocked up.

Start the tour → Read the written walkthrough

Every frame below is a real screenshot from the Fieldstone Supply Co. study - a genuine moderated session on real capture hardware, not staged data. Click any screenshot to see it full size.

01 / Set up & go live

Pick the rig. Pick the participant. Everything's already live.

A recording setup is configured once per lab, so a session starts from a picker, not a checklist. Before anything records, the idle previews show every camera and the meters show every microphone - aim, frame, and level-check with nothing on disk.

The Record page before a session: recording setup and participant pickers on the left, and live idle previews of both sources - the participant's screen and the participant camera - each with a moving level meter. — **Ready to record.** The two-source rig selected, both idle previews live - the participant's screen and the camera - level meters moving, and participant P01 picked. Nothing is on disk yet; this is the aim-and-level check.

02 / Record & log

Type the moment it happens. The timestamp is the first keystroke.

While recording, the main window becomes the researcher's logging surface: notes anchor to the instant you start typing, one-key tags file coded observations, and starting a task puts it on the clock. Remote observers log from their own devices into the same session, every note lands on the shared recording clock, attributed.

The Record page mid-session: the left column is the logging surface with a task picker, one-key tag chips and a note box, while both source previews show 2 of 2 sources rolling with the elapsed time. — **The Session Turn, seconds in.** The moment recording starts, the left column becomes the logging surface: the note box whose first keystroke marks the moment, one-key tag chips, the task picker - and beside it, both sources rolling on one clock.

The Observer Console dialog: a name field, a QR code to scan, the address and a six-digit PIN beneath it, and a remote-access block showing that internet access is switched off. — The join dialog a note-taker scans: QR code, PIN, one name field, no accounts. Remote access is off until you turn it on, and the dialog says so.

The Analysis page with the activity strip along the bottom of the window reading 'Transcribing audio: P04 - Jordan A.: 31%' beside a progress bar. — **Transcription runs itself.** After the session, speech-to-text and screen-text indexing work through the recordings in the background - the strip at the bottom is visible from every page and never in the way.

03 / Find the moment

Search it like a document. Scrub it like an edit suite.

Everything captured becomes one reviewable surface: speech and on-screen text are searchable, every click and note is a marker on the timeline, and the timeline zooms at the pointer from whole-session down to single seconds. Click anything - a search hit, a marker, a note, and the video is there.

The Review window: session rail on the left, the recording with its webcam picture-in-picture, a timeline underneath with a colored task band and speech and note markers, and the data view on the right listing timestamped notes. — **The docked workspace.** The task band and the speech and note lanes over the session, cluster badges counting where speech piles up, and every note in the data view a click from its moment. Click and keystroke lanes join in when the participant works on the recording machine itself.

The same timeline zoomed to eight times: the ruler now reads in ten-second steps, clustered markers have resolved into individual ones, and a navigator strip at the bottom shows which slice of the session is on screen. — **The timeline leaned in.** A ruler in seconds, clusters resolved apart, and the navigator strip showing where you are in the whole.

A search for the word error: the results list shows the on-screen Error 402 payment message and the participant's spoken reactions, each with its timestamp, with a note counting five more screen-text matches. — **Search lands on the moment.** One word - "error" - finds the on-screen payment message and the participant's spoken reactions, each a click from the moment itself, with the screen-text matches counted beneath.

04 / Compose & clip

Mark in. Mark out. The clip renders itself.

Highlights are marked while you watch and rendered in the background - composited exactly as your layout shows them. Stitch the study's clips into a reel for the readout without opening a video editor.

The layout editor: the webcam source selected over the screen recording with its resize grip showing, and an edit pane on the right with visibility, opacity and volume controls and a snap-to-edges checkbox. — **The layout, mid-edit.** The picture-in-picture source selected with the guides up, opacity and volume per source, and Save writes the arrangement back to the rig so every session on that setup opens this way.

The Review window seconds after saving a clip: the toolbar confirms the save, the data view's Highlights rows show the new clip rendering among the study's ready ones, and the Stitch reel button sits in the toolbar. — **A clip, seconds after Save.** The toolbar's receipt, the new highlight rendering in the background among the study's ready clips - it was at 83% when the light capture was taken and finished by the dark one - and Stitch reel one click away.

05 / Measure

Numbers with provenance.

Task timings come from explicit starts and stops; outcomes carry scores you define; SUS and SEQ are computed by the app from the participant's own answers. The product tracks how every number was measured, and refuses to average the ones that weren't.

The System Usability Scale results window: each SUS statement with a bar per answer option and the average score beneath, from three participants. — **Real bars, real counts.** The SUS, question by question, from the study's own participants - distributions and averages computed by the app, never asserted.

The Task outcomes editor: Success, Success with difficulty and Failure, each with a score and a problem-severity picker, and a plain-language line under each saying how it counts in the success rate. — **The outcomes editor.** Each outcome carries its score and its severity, a plain-words line says exactly what that score does to the statistics, and an excluded outcome is stated rather than hidden.

06 / Report & hand off

Findings drafted on your hardware. Data that leaves on yours.

The on-premises model drafts the stakeholder report, every claim cited and quote-verified against the transcript. And when it's time to hand off, one click exports the whole study: a CSV for the stats tools, and a self-contained HTML data table that opens anywhere with nothing installed.

The AI findings report window, on the section What got in people's way: Unclear error messaging during checkout, marked critical, with highlighted citation chips quoting participants and a severity line in plain words. — **"What got in people's way."** Severity in words, and every claim cited to a verified quote - each citation clicks through to the exact moment in the footage.

The Ask-the-study window answering What went wrong at checkout: a bulleted answer built from participants' verbatim quotes, each with a clickable session-and-timestamp citation. — **Ask the study.** "What went wrong at checkout?", answered only from the study's own data - every quote machine-verified against the recording, every citation a click from the moment.

The export - study data, self-contained

Not a screenshot. This is the study's real exported data table, embedded live - 456 rows of notes, task timings, survey answers and transcript, with the filters built into the file. It opens anywhere with nothing installed; scroll and filter it right here.

See it live instead.

A screenshot tour is the trailer. The demo is the film - your data rules, your hardware questions, and the whole loop run live in front of you.

Book a lab demo Browse the resources →