MADA Driver App
Mobile app for volunteer drivers delivering meals to families in need
Built for a Montreal community organization: volunteer drivers confirm availability, pick up boxes at the distribution window, follow an optimized route stop by stop, and mark each delivery done or report a problem — in English or French.
The app is a single cross-platform codebase that ships to both app stores. Drivers sign in with email, Google or Apple; routes, stops and households live in a managed database with access rules, so a driver only ever sees their own route. Dispatchers build the routes in a separate web console.
A delivery day is a guided flow: confirm availability for the next route, collect the boxes, then drive stop by stop on a map with the stop order optimized by a routing service. Each stop shows exactly what to hand over — item counts with diet codes, door codes, dispatcher notes, the household's languages — and one tap opens the phone's own maps app for turn-by-turn directions.
When something goes wrong there is no phone tag: the driver picks a structured reason (can't find the address, no answer, GPS issue) and the stop is marked for follow-up where dispatch can see it. A GPS check warns the driver when they are far from the pin, type is big enough to read at a glance, and the whole app works in English and French.
What you get with a project like this
- One codebase for iPhone and Android — a single app to maintain
- Sign in with email, Google or Apple
- Optimized stop order on a map, with one-tap handoff to turn-by-turn navigation
- Door codes, item lists with diet codes and dispatcher notes on every stop
- Structured problem reporting instead of phone calls
- Two languages with a one-tap switch
- Every delivery status lands in the database, live, for dispatch to see
Every moving part, in plain language.
Follow the arrows from the person using it to where the data lives. Hover any box to see what it talks to.
The app itself, installed from the app store. Shows the route, the stops and what to deliver.
Draws the map, optimizes the stop order and estimates drive times.
Routes, stops, households and delivery statuses. Access rules mean a driver sees only their own route.
Where routes are built, drivers are assigned and reported problems land.
What it costs to keep this online.
Building is a one-time price. Running it is a separate, usually tiny, monthly amount — here is where every dollar goes.
| Part | Per month | Notes |
|---|---|---|
Database & sign-in Managed SQL database with access rules and daily backups. | $25 | Managed SQL database with access rules and daily backups. |
Maps & routing Free tier covers a small fleet; grows with the number of drivers. | $5 | Free tier covers a small fleet; grows with the number of drivers. |
App store accounts Apple's yearly fee plus Google's one-time fee, averaged per month. | $10 | Apple's yearly fee plus Google's one-time fee, averaged per month. |
| Total | ≈ $40 / month | |
Full-size demo.
The Admin Console.
The other half of the system — where routes are built, drivers are assigned and every delivery is tracked live.
Want something like this?
Describe what is different about your situation and you will get an honest range and a plan.
Tell me about your project







