Long Earth SocietyLong Earth Society

Misc · Shelved · Oct 2026

The report button that can't exist.

The idea: one tap on a dashboard button, or a widget on the phone, to flag a speed trap or a wreck in the map app you're already using. All three big map apps take reports from drivers. None of them will take one from another app. The working answer turned out to be the button already on the steering wheel.

ONE-TAP REPORTPOLICECRASHwidget or dash buttonGoogle MapsApple MapsWazeno way infor other appsWHAT WORKSwheel voice button"report an accident"Siri · Gemini · Assistant → map app
The plan versus the wall. Every map app accepts reports, but only through its own screen or a voice assistant.

The idea

Reporting a hazard while driving means opening the map, finding the report menu and picking a category: three or four taps with your eyes off the road, which is exactly when you shouldn't be tapping. I wanted a big, dumb button. Two of them, really: Police and Crash. Press one and a report drops at your current location in Google Maps, Apple Maps or Waze, whichever you're navigating with. It could be a home-screen widget, or a cheap Bluetooth button stuck to the dash.

It started from the same place as Halftank's range circle: I wanted to add something to the map I already use, not ask anyone to switch apps.

The wall

Building the button would have been easy. Getting the report anywhere was the problem.

  • Apple Maps takes reports of crashes, speed checks and hazards (plus traffic, roadwork and closures in some places). You report from the map screen, from the Report icon in CarPlay, or by asking Siri. There's no route for another app.
  • Google Maps takes reports of crashes, speed traps, slowdowns, construction, lane closures, stalled cars and debris, through its own buttons. Google's developer map APIs are for putting maps and routes into your app; none of them files a report into Google Maps.
  • Waze runs on driver reports, but the only way in from outside is a partner data feed: approved partners, mostly cities and transport agencies, publish closures and incidents, and Waze's team reviews them. That's a pipeline for a transportation department, not a button on my dash.

My read on why: an open "submit a report" API would be a spam cannon. Anyone could drop fake police reports across a city. A report from inside the app comes from a phone the map knows is actually driving that road, which is what makes it worth trusting. Keeping the door shut is a reasonable call; it just kills this project.

What works: say it

Every platform did leave one hands-free door open, and it's voice.

  • Apple Maps: "Hey Siri, report an accident" or "Hey Siri, there's something on the road."
  • Google Maps: with Gemini in navigation, just say what you see: "I see an accident," "Looks like there's flooding ahead."
  • Waze: with Google Assistant on Android and Waze open, "Report police," "Report a crash," "Report hazard," and more.

And the physical button I wanted already exists. In most cars with CarPlay or Android Auto, holding the voice button on the steering wheel wakes the assistant. Press, say "report an accident", done. No hands off the wheel and nothing to build.

What I learned

  • Check the door before building the room. Confirm there's a way to write into the platform before designing anything that depends on it.
  • Reading a map is an API. Writing to one is a partnership. Map data is easy to get; putting data into someone else's map is gated, on purpose.
  • Voice is the integration the platforms chose. If you want to report something fast, the assistant is the button.

Status: shelved, and not for sale. The bigger idea it came from, Halftank's range circle, is still in progress.

Checked Oct 2026 against Apple's guide to reporting incidents in Maps, Waze's Google Assistant commands, the Waze partner data feed and Google's Gemini navigation announcement. Questions: Discord.