Drop: Delivery Logistic App

Brief & Research

After buying furniture that needed delivery and getting a timeline of 'between 9-5pm', I questioned why this still a standard practice. GPS tracking technology is readily available; we can streamline delivery turnaround time. This is why I conceptualized Drop, a delivery tracking app that will notify customers of their delivery within one hour time frame. Top researched app that helped the process are food delivery apps such as Ubereats, Doordash, and Pizzahut. 

Calling stores and inquiring about delivery timelines led me to understand two issues: One, they use third party delivery services; which is why none of them are trackable and are vaguely given a timeline of '9-5pm'. Two, there are two types of delivery drivers: short distance (paid hourly), and long distance (paid by distance). For this app, we are focusing on short distance deliveries as most customers buy delivery products within a local market.

How it works

Ideally, the system breaks down to three parts: Logistics, Delivery, Reception.

1. Logistic of route and products will be completed ahead. The truck will be assigned and loaded for the day's trip.

2. The driver will start the app with the assigned truck and follow the delivery list.

3. Customers await until the item is delivered.

Primarily for this project, I am only going to focus on #2: Driver delivery's perspective. This is because if we can better track the driver, we can optimize and confidently give customers the best drop off time. 

Initial Process

By reaching out to a couple of drivers helped me learn: 

As long as drivers make their deliveries within the day, they can do anything they want, including a plausible 3 hour nap.

My idea is to include a resting period/ break system within the deliveries. If we can track and take in account of when drivers take breaks, then we can properly streamline the time with accuracy. This is all up to the company's and government's allowance on breaks and have logistics to set up.

I start with jotting down my thoughts, then proceed to a lo fi and
med fi wireframes.


A customer will only receive a notification when the driver tap on Start. A link will be sent to them via email or sms.

I chose this since delivery services are from a third party, a customer won't be willing to download an app to track one delivery. Therefore delivery service will offer the one time tracking service. This isn't shown in the prototype because this project only focuses on Driver's side. 


There was a debate as to how the user’s delivery confirmation action should be. My original idea is to have a slider in the shape of a preset signature, but that idea wasn’t feasible. While testing with peers, there was a preference towards the 'yes' button as the call to action. But the reason I opposed this was to minimize accidental confirmations during the item drop off.

First Solution


After some testing, changes were needed to improve the user experience. Originally, I expected the company to give a general orientation of the app when they hire the drivers. Initial design suggested swiping left / right to access other screens User Profile, Full Route Map, unfortunately it wasn't 100% clear.

The user scenario assumed that drivers would mount their phones onto the vehicle's dashboard, hence CTAs were placed higher up away from the thumb's reach. But this needed to be updated because:

1. A lot of users may interact with their phone in their hands first, and mount at a later time.

2. The device might not be mounted at all to link it into their preferred GPS system to keep their phones free.

Visual embellishments were implemented as well. Below is the final result.


©2020 Clarice Wong. All rights reserved.