Skip to content

Screenshots

Capture the device screen from your computer. You do not need to touch the device, and images are not saved to its photo library.

  1. Select the device.
  2. Click Capture.
  3. The image is saved to the folder you selected.

The screenshot is the actual screen at native resolution.

Set an interval and a number of screenshots. KeyMob captures the screen repeatedly while the device is in use. Common uses:

Catching intermittent issues. A flicker that appears once in twenty scrolls is hard to capture by hand but easy to catch at 500 ms intervals.

Documenting a flow. Capture a full onboarding flow as an ordered, timestamped series.

Monitoring a long-running process. Capture a sync, upload or migration every ten seconds and review the series afterwards.

Recording a session remotely. The device can be in a test rig, in another room, or connected over Wi-Fi while someone carries it.

Pressing the side and volume buttons works for a single image. It is less suitable when:

  • Both hands are needed to reproduce the bug.
  • The button press interrupts what you are capturing, such as a drag, a long press or a transition.
  • The images must be moved off the device, which means going through the photo library of the device owner.
  • You need many images at a fixed interval.
  • Keep the screen on. If the device sleeps during a series, the remaining images show the Lock Screen.
  • Use USB for short intervals. Wi-Fi adds latency and jitter. Intervals around 200 ms are not reliable over Wi-Fi.
  • Plan for storage. A long series at native resolution on a large-screen device uses significant disk space.
  • Nothing is saved on the device. Images go directly to your computer, which makes this the right way to capture someone else’s device.

A screenshot series together with a performance capture makes a clear bug report. It shows both the frame-rate drop and what was on screen at that moment.

Simulated location · Device information · Performance monitoring