The Map That Tells Your Story
A few months after launch, a Lyft driver messaged us. She'd been hit by a car that ran a red light, and our app had captured it. But when she sent the clip to her insurance company, they asked a simple question: where exactly did it happen? She knew the intersection. The video knew the intersection. But there was no clear way to show it.
The gap we didn't see coming
We built Hawk to be a court-ready dashcam for your phone. SHA-256 hashes on every clip, GPS timestamp overlay, one-tap export to a dispute ZIP with a manifest that's signed and verifiable. On paper, it was bulletproof. In practice, there was a moment we'd overlooked.
When you hand evidence to an insurance adjuster or a police officer, they're looking at a video file. They can see the timestamp and the speed overlay. But they're watching it on their desk, maybe in an office with no context about the road layout or the sequence of turns leading up to the incident. That Lyft driver had to describe it verbally. "It was on Fifth Avenue, near the corner of Main." It worked, but it felt weak for a piece of evidence that was otherwise rock solid.
We realised that the same GPS data we were already recording could be drawn as a polyline on a map. Not a real-time tracker, not a fleet tool. Just a visual representation of the journey the moment it happened.
Building replay without the bloat
The tricky part wasn't the map itself. MapKit on iOS and Android mapping libraries are mature. The tricky part was keeping it honest to what Hawk is.
We could have built a connected system where every trip auto-uploads and you can replay your routes from a cloud dashboard. That's what fleet-management platforms do. But Hawk isn't a fleet tool. You own your clips. They live in your Evidence Locker, biometrically locked on your phone. If you're a Rideshare Pro user, locked clips sync to your own iCloud account, not our servers.
So we built trip map replay as a local feature. When you open an evidence clip, you see the polyline drawn from your GPS breadcrumbs. It's there in the app, tied to that specific moment. You can see the route, the start and end points, where the incident sits in the geography of your drive. When you export that clip as a dispute ZIP, the map data travels with it as part of the manifest.
It's not fancy. But it means an adjuster looking at your evidence can see not just what happened, but where, and how you got there.
Why this matters for the dispute
Insurance disputes live in a grey zone. You have your story. The other party has theirs. The dashcam footage is the truth, but truth without context is just pixels.
A trip map does something almost invisible: it removes one layer of doubt. Not because it adds drama, but because it supplies a second vector of proof. You're not just saying "I was hit at Fifth and Main." You're showing your route, your speed, where you were in relation to traffic signals and cross streets. It becomes harder to argue with.
We've watched police reports and small-claims filings go smoother when the claimant can hand over not just a video but a video with a clear geographic trail. The trip map doesn't convict anyone. It just makes the evidence stick.
The user who made us think differently
That Lyft driver came back a few weeks after trip map replay shipped. She'd sorted her insurance claim. She told us the map detail made the difference in how quickly the adjuster moved. She didn't need to describe the road anymore. The app did it for her.
That's when we realised we'd been thinking about Hawk in layers. The first layer is the recording itself, with cinematic optical-flow stabilisation and bulletproof hashing. The second layer is the Evidence Locker, the biometric lock, the dispute export. But the third layer is context. The map isn't a feature that belongs in a fleet tracker or a subscription cloud service. It belongs in the hands of someone who needs to prove what happened, standing alone in front of an adjuster, a police officer, or a judge.
What we didn't build
It's worth saying what trip map replay isn't. We didn't build a real-time tracker. We didn't add the ability to share your route live with someone else. We didn't create a connected service where your location data lives in our servers. Every map lives on your device, in your clips, in your control.
Some of this is product discipline. Some of it is privacy. We're GDPR-aware, and we know that location data is sensitive. If you use Hawk and you want the GPS overlay on your clips, you choose that in your profile settings. The trip map sits inside that choice.
The feature is also not a replacement for what a professional dashcam can do. A mounted Viofo or BlackVue will record in weather conditions that might kill your phone's battery, and they integrate with your car's power. Hawk runs on your existing iPhone or Android. It's for commuters and rideshare drivers who need evidence without buying new hardware.
When you're building evidence into a smartphone app, every detail matters because someone might hand that export to a person who decides what happens next. What else should dashcam evidence include before it reaches that moment?