Groceries delivered
in real time.
One Flutter codebase, four roles. ONOA connects customers, riders, and store owners on a single real-time map — with MercadoPago checkout, photo-verified drop-off, and a rider earnings dashboard. Android, iOS, and web from the same source tree.
Delivery platforms usually ship as a fractured stack — a customer app from one vendor, a rider app from another, a store dashboard bolted on the side, and an admin panel nobody enjoys using. Communication between them leaks: assignments end up on WhatsApp, status updates arrive ten minutes late, and customers refresh the map because they don't trust "on the way."
The client wanted the opposite. One platform. One codebase. One real-time source of truth. Local payment (MercadoPago) baked in from day one — not tacked on later. Photo-verified drop-off so nothing disappears at the door.
And it all had to run on a budget that a small city delivery service could afford. No enterprise stack. No per-seat licensing.
A single Flutter codebase covering Android, iOS, and Web. Clean architecture — data / domain / presentation — with BLoC for state and GetIt for dependency injection. go_router handles role-based navigation so the same binary serves four completely different UIs based on who logged in.
Firebase Authentication handles the four roles with a single login flow. Firestore is the real-time source of truth — rider GPS, order status, assignment state, all synchronising live. When a rider marks "picked up," the customer's map updates in under a second.
Live GPS pushes every few seconds from the rider's phone; customers see the scooter pin move on flutter_map. At drop-off, the app requires a location-verified photo before the delivery can be marked complete — no location match, no completion.
MercadoPago runs through an in-app WebView with full transaction status handling — a returned "success" isn't trusted until the webhook confirms.
Riders get their own dashboard powered by fl_chart — completed deliveries, income, weekly trends. All in the same app that assigns them work.
What we built it with.
The intelligence layer.
From brief to production.
What shipped.
One app for everyone. Riders don't need WhatsApp for assignments anymore. Store owners don't call to check on orders. Customers stopped refreshing the map. That's what live means.
More from the studio.
AXCEL POS
Restaurant floors can't wait for a spinner. Our client needed a point-of-sale that would take orders and print receipts even…
View case study →
Live
formed
A private in-home training service in Tampa Bay needed a platform that felt more like a members' club than a…
View case study →
Live
Prima Portal
Primaresearch was distributing paid datasets by email — no version history, no audit trail, no way for clients to preview…
View case study →Building something similar?
If your problem lives at the intersection of AI, product, and real business constraints, let's talk.
