Processed locally
- High-frequency motion readings
- Three-second gravity-aligned vertical roughness calculations
- Filtered impact detection and severity
- Drive distance and live app statistics
Data transparency
Sucky Roads is built to measure pavement, not people. These are the Android and iPhone public betas’ combined live aggregate totals and the categories of information used to build the road map.
On-device processing
High-frequency motion readings are processed on the device into compact road samples and probable-impact events before upload.
The app generates a random identifier so uploads from the same installation can be grouped during beta testing. It is not a phone hardware or advertising identifier. The server stores a one-way hash of it.
The public map uses road-condition evidence only. It does not expose installation identifiers, individual device histories, or the private batch records used for beta diagnostics and Fleet planning.
Why these fields exist
Location, accuracy, speed, and event time place evidence on the correct stretch of pavement.
Speed-adjusted vertical roughness, impact strength, and repeat passes produce a continuous 0–100 road score. One isolated jolt cannot assign the worst rating to an entire road.
Network type, batch size, and bandwidth counters help size future Fleet cellular plans.