EMS Dispatch & Firewatch CM: Mobile Platforms for Emergency Response

EMS Dispatch and Firewatch CM are sibling public-safety platforms we designed and built in-house, both currently in beta. EMS Dispatch is a civilian medical SOS and first-response system; Firewatch CM is a community-powered fire reporting and dispatch platform. In cities where there is no unified emergency number infrastructure, the phone in a bystander's pocket is the fastest sensor available - if the software is built for it.

Emergency reporting apps face two hard problems. First, false or duplicate reports: a single fire generates dozens of reports of varying accuracy, and responders cannot chase all of them. Second, the reporting side and the response side are different products with different users - a panicked civilian and a professional dispatcher - that must nonetheless share one real-time picture.

Both platforms are dual-interface by design: a civilian-facing mobile app for one-tap reporting, and a full-screen agency queue with a live incident tracker for dispatchers. For EMS Dispatch, civilians report medical emergencies with background GPS and severity indices; a panic SOS protocol alerts emergency contacts with an automated SMS fallback, and the app includes a searchable first-aid database (cardiac arrest, burns, drowning, poisoning) and a nearby-hospitals finder - so the app is useful before responders arrive. For Firewatch CM, we attacked the false-report problem algorithmically: incident reports are clustered, and when report density within a 1.0 km radius over a 30-minute window crosses the threshold, the incident is auto-verified and escalated into the agency queue. Community upvote/downvote verification adds a human signal. Dispatchers work from a dedicated console with live GPS synchronization.

Flutter and Dart on both apps - Riverpod and GoRouter on EMS Dispatch, Provider on Firewatch CM; Firebase Auth for identity; Cloud Firestore for real-time incident state; Flutter Map and Google Maps for live tracking.

Both platforms enforce role separation between civilians, agents, and dispatchers - agency consoles and admin panels are gated by authenticated roles, not hidden URLs. Location data is used for dispatch and clustering, with privacy controls exposed in the app settings. Firestore access rules restrict reads and writes by role, and reporting flows are structured to limit abuse: clustering and community verification mean a single malicious report cannot trigger a dispatch on its own.

Both platforms are functional in beta: end-to-end flows from civilian report through algorithmic verification to agency dispatch queue work today, on real devices, over real mobile networks. The clustering-verification design gives responder-side users a queue of credible incidents rather than raw noise - the core requirement for agencies to trust a community reporting system.

Designed and built in-house by our mobile engineering team as part of our public-safety product line (alongside ARIA I and ARIA II). Both products are in active development toward agency pilots.