/ Sailor Delivery
Hyperlocal delivery
A three-sided delivery system, live in 28 days.
Delivery ecosystem with Customer, Rider and Admin surfaces: live order tracking, rider earnings, wallet management, notifications and operations.
- MOBILE
- Built in 28 days
- Flutter · Firebase · Android · iOS
/ the idea
From idea to product.
Hyperlocal delivery only works when the customer, the rider and operations stay in sync. Sailor needed more than a customer app. It needed an order loop the whole network could run on.
/ the problem
One order had to survive three different products.
Customers place and track orders. Riders accept, navigate and collect earnings. Ops needs oversight when something slips. The hard part is keeping that state consistent in real time.
/ what we built
Product surfaces that shipped.
Customer experience
- Place delivery orders
- Follow live order status
- Get notifications through the journey
Rider experience
- Accept and manage deliveries
- Live navigation support
- Rider wallet and earnings
Operations
- Delivery management
- Admin oversight of orders and riders
- Notifications across the network
/ the product
What it looks like.
/ the build
28
days · kickoff → production
Over four weeks we defined the order loop, designed the customer and rider journeys, built the Flutter apps with Firebase, and stood up the admin surface so ops could run the network.
01
Product definition
02
UX / UI
03
Development
04
Testing
05
Deployment
/ under the hood
Stack that served the product.
- Flutter
- Firebase
- Android
- iOS
/ what shipped
Concrete deliverables.
- Customer app
- Rider app
- Admin dashboard
- Real-time order tracking
- Rider wallet & earnings
- Notifications
- Live Google Play release
Have something like this in mind?
Tell us what you’re building. We’ll help figure out what it takes to get it live.
Tell us what you’re building →
