Geolocation, Sensors & Device API Dashboard
Device sensors are fragmented across six different APIs, each with its own event model and permission flow. This dashboard unifies them — request permissions, stream live telemetry, and inspect the exact JSON payload of every event. Great for mobile web, IoT, and AR/VR development.
Tool interface
Each sensor starts independently. Motion and orientation on iOS require a user gesture and HTTPS. Some sensors are only available on mobile devices.
Introduction
Building for mobile web, IoT, or AR/VR means working with device sensors — but the APIs are scattered and inconsistent. This dashboard brings Geolocation, orientation, motion, light, battery, and vibration into one place so you can verify what your device actually exposes.
How It Works
- Each sensor is feature-detected on load and marked supported or not.
- Starting a sensor requests permission (including iOS's gesture-gated flow) and attaches an event listener.
- Live values render into readout metrics, and the raw event object is pretty-printed as JSON.
- "Stop All" detaches every listener cleanly.
Privacy
Sensor data is read and rendered entirely in your browser. Nothing is transmitted. No API calls, no tracking.
Limitations
- Many sensors are only present on mobile devices with the relevant hardware.
- iOS requires a user gesture and HTTPS for motion/orientation.
- AmbientLightSensor support is limited and may require browser flags.
- Battery Status is unavailable in some browsers for privacy reasons.
FAQ
Why does orientation/motion show "Unsupported" on my iPhone?
iOS 13+ requires you to call DeviceOrientationEvent.requestPermission() from a user gesture. Tap "Start" and approve the prompt. Also ensure you're on HTTPS.
Is my location data uploaded?
No. All sensor data stays in your browser and is never transmitted anywhere.