Case study

ShipSense — IoT Cargo Monitoring

Real-time cargo monitoring, designed for managers on the move.

Role
UI/UX Designer (solo)
Timeline
2 weeks · June 2026 (redesign of 2024–25 academic project)
Tools
Figma
Mobile AppIoTDashboardPrototypeDark UI
ShipSense driver app showing live shipment tracking on a map
The problem

What it solves

Logistics managers struggle with fragmented data and delayed notifications about cargo conditions — temperature, humidity, location. By the time a problem reaches the manager, the cargo may already be compromised. ShipSense centralizes real-time IoT sensor data into a single intuitive dashboard so issues surface immediately and the team can respond before loss occurs.

The approach

Key design decisions

01

Status-driven dashboard

Prioritized a Critical Alerts section at the top of the home screen so high-priority issues like temperature spikes are the first thing the user sees — no hunting through menus when seconds matter.

02

Modular tracking cards

Each shipment gets a compact card with the essentials — ETA, current location, status, temperature, humidity — to reduce cognitive load while keeping the most relevant data visible.

03

Data visualization

Used clean, color-coded indicators for sensor data so users can spot trends and anomalies at a glance, without parsing raw data logs.

The screens

Inside the prototype

Shipments list with status, temperature and humidity per shipment
Shipments list — status, temperature and humidity at a glance.
Active alerts modal showing 4 prioritized alerts over a map
Active alerts — color-coded by severity, surfaced over the live map.
Live tracking screen with delivery timeline from Booked to Delivered
Live tracking — driver, route and delivery timeline in one view.
The outcome

What shipped

Developed a high-fidelity interactive prototype with a complete end-to-end tracking flow. The design focuses on zero-latency information retrieval for fast-paced logistics environments — every screen is built around the principle that the user should never have to dig for critical information.

Reflection

What I learned

Complexity vs. clarity

Learned how to balance high-density technical data with a clean UI by using progressive disclosure — show summary first, full data on tap.

Designing for the field

Realized that field users (warehouses, on-the-go) need high-contrast buttons and large tap targets — accessibility under glove, glare, and motion.

Want to see more, or work together?