UN WFP Logistics Cluster
An offline-first field app for the UN World Food Programme and the Global Logistics Cluster, helping humanitarian teams coordinate food, medicine and cargo where networks and infrastructure fail.
- Role
- Lead Product Designer and Design System Owner
- Users
- UN staff, coordinators and local partners
- Platforms
- iOS and Android in two device tiers, plus an admin dashboard
Before the app, operations ran on laptops, heavy spreadsheets and web tools that barely worked on site. Field teams needed a mobile-first product that works from a phone, without a stable connection or a desktop nearby.
Interviews showed that UN staff carry modern phones, but the local partners they work with often use old, slow Androids on 2G. The app had to work for both:
- 360 px minimum screen width.
- 1 GB RAM minimum, Android 8+.
- Report flow works 100% offline.
- Average report payload of 38 KB, small enough for 2G.
- Offline map tiles, with the cache capped at 250 MB.
Lead Product Designer and Design System Owner, with end-to-end design direction: research, product architecture, the design system, the mobile experience for two device tiers, the admin dashboard, documentation and developer handoff.
Field operators capture and verify, coordinators prioritise and route, and local partners report and share. All three enter Mission mode and feed one operational picture.
- CaptureWorks without signal.
- CompressMedia and payload shrink for 2G.
- QueueSafe local state on the device.
- SyncSent as soon as the network returns.
- UpdateThe shared operational picture refreshes.
Hypothesis. We believed that if the report flow worked fully offline and fit low-end phones on 2G, local partners would report regularly, not only UN staff. It held: after the Lite version launched, the share of field teams reporting regularly grew from 25% to 33%.
Instead of one compromise, we built two experiences on a shared core:
- Lite for low-end phones: a pinned “Submit report” button within thumb reach, compact tiles, short labels, no live feeds and no background data.
- Full for modern devices: live “Near you” alerts within 50 km, HD photos (up to 5 per report), full labels and richer updates.
Same design system, same codebase, same report flow, same offline queue.
140+ components and variants, one visual language for both tiers: Open Sans on an 8-pt grid, AA contrast tuned for bright sunlight, 48 px touch targets and dedicated components for offline, sync and emergency states.
Reports with photos, GPS and constraint type (road blocked, bridge out, passable) flow into an admin dashboard. There, logistics teams see the live map, warehouses, priority routes and the full pipeline from signal to verification, routing and dispatch.
- Monthly reports +32%, from 973 to 1,284.
- Share of field teams reporting regularly grew from 25% to 33% after the Lite version launched.
- 2,460 active devices, including 1,130 low-end phones: 2× reach.
- Average time to dispatch −38%, from 6.8 h to 4.2 h.
- 124 → 48 → 21 → 12: weekly reports captured, verified, routed and dispatched in one pipeline.
How we measured: in Google Analytics over the four months after release. Results reflect the work of the whole product team.
The product became a multi-year partnership with the UN logistics division. Today it’s an internal tool used by humanitarian teams worldwide and available in both app stores. logcluster.org
- Offline-first
- Low-end Android
- iOS and Android
- Admin dashboard
- Design system
Test with both groups on their own phones, earlier. UN staff flew in with modern phones, while the local partners who filed most reports used old Androids on 2G. We learned how far apart the two groups were through interviews, and the two device tiers came after that. Today I would go to the field and test on real devices in the first weeks, so the split between Lite and Full would shape the product from the start.