The FuelBuddy Driver App is what drivers use to actually deliver fuel to customers. Building for drivers is its own kind of problem: the screen has to be readable in direct sunlight, taps have to be forgiving, and the network can drop at any point on the road. I built a set of features end to end aimed squarely at those conditions — frontend and the data APIs behind them.

What I built

Offline-tolerant UI: Drivers regularly lose signal, so I cached route and order data locally and let them keep working through dead zones. The app queues changes and syncs them back once the connection returns, instead of freezing.
Location and maps: Handled the frontend for live GPS tracking and map routing, keeping frequent location updates and map redraws efficient so they didn't drain the battery over a long shift.
Field-friendly UX: Owned several operational features end to end, designing them for real conditions — high-contrast layouts, large tap targets, and short forms so drivers can log a delivery quickly and safely.
The APIs behind them: Built the CRUD APIs these features read and write to on Hasura's GraphQL engine, so I could ship a feature end to end — the offline queue, order data, and delivery logging all talk to endpoints I owned.

Why it mattered

Designing for a phone-in-hand, on-the-move context made the app faster to use in the field. Drivers could focus on the road and the delivery instead of fighting a laggy screen, which kept deliveries moving.