1Pat's complaint
This started because my friend Pat complained, at length, with photos and with the conviction of someone whose suspension had recently suffered, that Halifax roads were terrible. He wasn't wrong. What made it something I could act on was his idea: an app for reporting potholes and seeing them on a map, instead of burying the problem in a municipal inbox.
I liked it partly because it was useful and partly because it gave me an excuse to work with maps, image uploads and phone location services. Civic tech usually gets described as noble. This was also technically convenient, which is a more honest account of how a lot of side projects start.
2Tinder for potholes
The first version was deliberately simple: get the location, take a photo, give it a severity score, submit it and see it on a map. There's a quick-report path for speed, a detailed report for when you have more to say, and a map for browsing what's already been logged.
The more interesting part was community validation. Instead of taking the first reporter's severity score as final, the app could show existing pothole photos to other people and ask whether they agreed with the rating. That made a low-effort feedback loop somewhere between moderation and a civic version of Tinder, which is an absurd sentence and an accurate product description.
3What the prototype does
I have a habit of telling this story like I built municipal infrastructure. I didn't. I built a good prototype with the right seams: onboarding, quick and detailed reporting, map browsing, photo capture and reports packaged for email to Halifax 311. That's a fair amount of product for something inspired by Pat complaining about his car.
Table 1. What's in the prototype.
| Module | What it does |
|---|---|
| Quick report | Grab GPS, severity, and a short description with minimal friction |
| Detailed report | Attach photos, location context, and more descriptive evidence |
| Map view | Visualize reported potholes across Halifax with severity cues |
| Admin dashboard | Provide a cleaner operational view for triage and follow-up |
| 311 handoff | Package the report for direct email-based submission instead of burying it in notes |
The other correction is about architecture. The prototype stores everything on the phone with AsyncStorage, rather than pretending a city-scale backend is humming away somewhere. Supabase is the natural next step for syncing between users and real-time updates, but the prototype isn't there yet and doesn't claim to be.
4The hard parts
The obvious unsolved problem was moderation. Let strangers upload images and some of them will upload things that aren't potholes. Doing that well takes policies, review workflows and probably some machine help. The app was never meant for a full public launch, so I got to stop just before the part where the internet finds your upload button.
It also sat somewhere between useful and absurd. A pothole app sounds like a joke until you spend an afternoon driving around the city photographing crater-sized holes and realize the data is actually valuable. At that point it's field research.
The production checklist is the whole business in miniature: proper 311 routing, real syncing, notifications, crash reporting, analytics. Those are the unglamorous systems that turn a fun prototype into software other people can depend on, and they're where a lot of civic-tech ideas find out they've turned into an operations job.
5Driving around with Pat
Pat and I did end up using it for real, driving around Halifax logging potholes and then sending the city a detailed report. That afternoon matters more to me than whether the app ever launched. It produced something real about a local problem, and Pat got to feel his complaint had been taken seriously by at least one person with a React Native dev environment.
Hole Patrol reminded me that civic tech doesn't have to become a company to be worth doing. Sometimes it's enough to take something everyone already knows is broken and give the complaint coordinates, photos and a cleaner subject line.

