Stand where the problem is.
Name the room, describe the complaint, and capture 30 seconds of the device’s connection and supported network checks.
Give your engineer more than a complaint. Capture a short view of one device’s connection, make a change, and compare what happened.
A gift to the public. No account. No activation. No license.
In development · Public builds are being prepared.
Same device. Same place. 30 seconds each.
| Measured evidence | Before | After |
|---|---|---|
| First response | 3.8 s | 0.8 s |
| DNS response | 620 ms | 34 ms |
| AP changes observed | 2 | 0 |
| Signal · median | −67 dBm | −59 dBm |
Example data. Request timing is not full page-load time. Observations alone do not establish cause.
When a room full of guests has a problem, event staff and engineers need a common starting point. Snapshot is being built to make that conversation easier.
Name the room, describe the complaint, and capture 30 seconds of the device’s connection and supported network checks.
Take another snapshot from the same spot. Compare signal, observed AP changes, response timings and the evidence each platform can provide.
The planned export includes a readable report and AirWitness-compatible snapshot files, so the investigation can continue.
Snapshot focuses on what this device could observe during this capture. A missing measurement stays missing.
Try the Android, Windows & Mac interface concept →Look for observed AP changes and disconnects during the window. A short capture cannot provide a complete roaming history.
A planned factor breakdown shows how the estimate was calculated and which inputs were unavailable. The Wi-Fi score is separate from connectivity checks.
Compare supported DNS and request timings with the connection evidence. One timed request is not a browser page-load test.
Windows, macOS and Android are the first targets. Public installers will appear here once each build is ready. No registration or license will be required.
For the laptop you already take on site.
Public build in preparationFor your Mac at the venue or the support desk.
Public build in preparationA portable view of the guest’s connection.
Public APK in preparationAndroid will be distributed here as a direct APK download while we work toward Google Play. The experimental measurement lab is not a public Snapshot release.
Once the public APK is available, download it directly to your Android device. Open the file and, if Android asks, allow that browser or file manager to install this app. That permission can be turned off again afterward. No root access or bootloader changes are needed.
Yes. Snapshot is a gift to the public. The planned Windows, macOS and Android versions have no account, activation or license requirement.
No. Snapshot is the focused capture, compare and handoff tool. The full AirWitness application provides a broader troubleshooting workspace. Snapshot v1 is being built to read and write compatible snapshot files in both directions; it may display only part of a richer AirWitness file.
It records one client’s experience at a particular place and time. It does not measure every guest, access-point load or venue-wide capacity. It gives engineering a concrete piece of evidence to investigate.
Android requires location permission and enabled location services for certain Wi-Fi observations. Supported measurements vary with Android version, device hardware and permissions. Unavailable information will be labelled accordingly.
The planned capture workflow keeps evidence on your device until you choose to export or share it. Connectivity checks make requests to the configured test services, which receive the source IP and ordinary request metadata. This landing page uses no analytics scripts or tracking cookies. See the AirWitness privacy policy for website logging and service information.
Linux is planned for a later phase. iOS is not part of the first release; its available Wi-Fi observations differ substantially.