On-demand roadside assistance — maps, urgency, and “someone near me”
A small Flutter exercise in connecting a stranded driver story to providers on a map-backed surface, with Firebase in the mix for the kind of quick backend you reach for when you are still learning how products feel in motion.
If your car stops, you should not have to decode a dozen menus before help is on the way. This app was my early playground for that narrative: pick a need, see proximity, lean on maps, and keep the flow bluntly obvious.
Three beats — not a full case study. A reference for how I think about growth.
Spark · then
I was proving I could wire Flutter to Maps and Firebase and still tell a clear story: panic → action → relief. The code was smaller than what I ship today; the curiosity was real.
Lesson · what stuck
Users do not admire your stack when they are stuck on a road—they trust clarity, speed, and honest UI states. That lesson carried straight into later work where maps are the primary surface.
Trajectory · toward
Today I build map-first products with routing, roles, and resilient fallbacks. This app was the warm-up sketch; the discipline (permissions, errors, real routes) is where I levelled up afterward.
If you only judge engineers by their shiniest repo, you miss velocity of improvement. This page exists so you can see a deliberate breadcrumb: same person who sketched roadside urgency later architected multi-role, map-heavy systems with grown-up boundaries.