- 10,000+downloads
- iOS + Androidone Flutter codebase
- ~1 yearand still ongoing
- 4 people2 app, 1 backend, 1 QA



The client
A private founder in Lahore who wanted a safer way for women to travel in the city. (The client asked not to be named.)
My role
I’m one of two Flutter developers on a team of four, with one backend developer and one QA engineer. My work is enhancing the app, fixing issues as they come in from real rides, and QA before each release.
The hard part: real time, to the right person
A ride app is only as good as its live data. Three things had to work every time:
- Live tracking. The passenger sees the driver move on the map, and the driver sees the pickup point, with no stale positions.
- Bids on time. When a passenger posts a ride, bids from drivers have to arrive within seconds, or the passenger gives up and the driver loses the fare.
- To the exact user. Each bid and each status update has to reach the one driver or passenger it belongs to, not a neighbour, and not twice.
What we did
- WebSockets for live data. We moved tracking and bids onto a WebSocket connection, so updates are pushed the moment they happen instead of being polled.
- A cleaner architecture. We restructured the real-time code so that connection handling, ride state and UI are separate layers. That made it clear which part owns a bid or a location update, and made bugs much easier to find.
- Testing in every sprint. Real-time flows were tested each sprint, with our QA engineer, on real devices and real rides, and issues were fixed before the next release.
Result
The app is stable in production and has passed 10,000 downloads. Work continues on new features and on keeping the ride flow fast and dependable.
SheDrives
Ride-Sharing · Safety · iOS & Android
10K+ downloads
Download it and see the work for yourself.
Building an app with live tracking, chat or real-time bidding? I’ve done it in production. Read how to build live location tracking in Flutter, see Flutter app development, or tell me about your project.