Water logistics · 2026 · iOS + Android
Tanker
Premium water by tanker. Reorder, live miles from dispatch to door, and a rating operations can actually use.
Technical Product Owner + Mobile Engineer
Live tracking
Dispatch to door
Reorder
Last delivery, one tap
EN / AR
Built for the Gulf
Click any screen to zoom
01
Context
Tanker is a consumer and household product for potable water by tanker — 5000L class deliveries, address-based, with live tracking from dispatch to door. The market is Gulf (onboarding in EN/AR, SAR on orders). Trust is the product: verified drivers, handshake confirmation, digital invoices, then a structured rating.
02
My role
I owned
- Onboarding narrative and EN/AR first-run
- Order, track, reorder, and rating loop
- Home education (tank tips) vs. operational orders
- Flutter implementation of tracking and order history
The team owned
- Fleet dispatch and GPS
- Driver app / ops console
- Invoicing and payments
03
The problem
Ordering a water tanker is still a phone call in many households. You do not know where the truck is, you reorder from memory, and if the delivery is poor there is no structured feedback. For a premium water promise, that opacity is the whole problem.
04
Discovery
The first session has to teach the promise: watch every mile live; delivered with trust. After that, Home is order + order-again (last product and volume) + tips. Orders is a filterable history (All, Active, ASAP, Scheduled) with status colour, volume, and price. Rating is not a single star — it is tags that ops can actually read (on time, clean tanker, careful delivery).
05
Product decisions
Trust before the map
- The decision
- Onboarding leads with live tracking and verified drivers / handshake / invoices — not a feature tour of settings.
- Why
- People already know how to order water. They do not believe they will see the truck.
- The trade-off
- Longer first run. Skip is available so we do not trap anyone.
- The result
- The brand is set before the first Order water tap.
Order again is a first-class card
- The decision
- Home surfaces the last potable 5000L order as a one-tap repeat, next to a new order CTA.
- Why
- Water is recurring. If reorder takes a full form, they will call instead.
- The trade-off
- New addresses and new volumes need a longer path. Repeat households are the volume.
- The result
- The habitual job is one tap. The exceptional job still exists.
Ratings as operations data
- The decision
- After delivery, rate the named driver, tagged reasons, optional note, tied to an order ID.
- Why
- A 5-star average with no tags cannot train a fleet.
- The trade-off
- More taps than a single star. We allowed Maybe later so we do not block the app.
- The result
- Ops can see “clean tanker” vs. “on time” instead of a vanity score.
06
UX / user flow
Photography-led onboarding, EN/ع toggle, then a blue-and-white operating system. Home: add address, order water, order again, tips for the tank. Deliveries: track copy, filters, completed vs. cancelled stripes, SAR totals. Bottom bar: Home, Orders, Support, Account, with a water-drop FAB.
07
Technical architecture
Flutter client, order and tracking APIs, bilingual UI, push for live status. Driver identity and verification are backend facts surfaced in rating. Invoices are digital artifacts of the same order object used for tracking and reorder.
08
What I built
- EN/AR onboarding
- Home: order, reorder, educational tips
- Delivery list with status, volume, price, order ID
- Live-tracking promise in product copy and orders surface
- Structured delivery rating with tags
09
Trade-offs
We did not build a public driver marketplace. Fleet is the company’s. Multi-stop commercial accounts waited. The household loop — address, 5000L, track, rate — had to be airtight first.
10
Launch
Customer Flutter app for iOS and Android in a Gulf water-delivery context (SAR, Arabic toggle, tanker photography).
11
Outcome
Households can order potable water, see deliveries as a history they can filter, and rate a named driver against a specific order. Fleet utilization numbers stay with operations.
12
What I learned
Logistics consumer apps are won on reorder and trust, not on map polish alone. I would have instrumented time-to-reorder and rating completion before adding more home content. Tips are nice; a dry tank is the only emergency.