Screenshots

Take the device’s screen without touching the device, and without the image going through anyone’s photo library.

A single capture

1. Select the device.
2. Press capture.
3. The image saves to the folder you chose.

The result is the real screen at native resolution — not a re-render, not a mock-up.

On a timer

Set an interval and a count, and KeyMob captures repeatedly while the device is used. This is the feature that earns its place:

Catching something intermittent. A flicker that appears once in twenty scrolls is very hard to screenshot by hand and trivial to catch at 500 ms intervals.

Documenting a flow. A series through a whole onboarding, in order, timestamped.

Watching a long-running state. A sync, an upload, a migration — capture every ten seconds and read the sequence afterwards.

Recording a session you are not holding. The device can be in a rig, in another room, or connected over Wi-Fi while someone walks a route with it.

Why not the device’s own screenshot

Side-plus-volume works fine for one image. It falls down when:

• You need the hands free, because both are busy reproducing the bug.
• The gesture itself disturbs what you are capturing — a drag, a long press, a transition.
• The images have to leave the device afterwards, which means the photo library, which means a person’s photo library.
• You need thirty of them at a fixed interval.

Practical notes

• Keep the device awake. The screen has to be on. A device that sleeps mid-series captures the lock screen for the rest of it.
• Cable for tight intervals. Wi-Fi adds latency and jitter; at 200 ms the interval stops being reliable.
• Full resolution costs space. A long series at native resolution on a Pro Max adds up quickly.
• Nothing is written to the device. Images go straight to your computer, which is also why this is the right way to capture someone else’s handset.

Pair it with a capture

A screenshot series alongside a performance capture is the most convincing bug report available: the frame-rate dip and the picture of what was on screen when it dipped, in the same ticket.

Next steps

Simulated location · Device information · Performance monitoring