7 September 2025
The driver app
After eighteen months of saying "no, drivers can use the regular dashboard", we caved and built a dedicated driver app. Three reasons we changed our mind, and what shipped.
Why we said no for so long
Most platforms ship a driver app on day one because it's easy to demo. Ours wasn't a priority because the dispatch tab on the regular Floree dashboard worked — drivers logged in on their phone, saw their list, marked deliveries done. Worked fine for the first 80 shops.
Why we changed our mind
Three things accumulated:
- Battery. The regular dashboard is a full Next.js app. On a delivery driver's 4-hour shift it ate 35% battery. The native app eats 8%.
- Offline. Drivers go through buildings with no signal. Marking a delivery done required signal; if it didn't complete, the delivery showed as still-pending. Several drivers learned to work around it; the system got noisy.
- Photo capture. Customers want a photo on delivery, especially for corporate accounts. The web flow was four clicks; the native flow is one.
What shipped
- iOS + Android native apps in the stores
- Offline mode with sync — drivers can mark deliveries done without signal, syncs when they're back online
- Photo capture with one-tap upload, GPS-stamped
- Route optimization — the day's deliveries auto-routed for shortest distance
- Driver leaderboards for shops with multiple drivers — gamified, opt-in
Available to every Pro tenant. Drivers don't need a separate Floree login; same credentials as the dashboard.