An app to make delivering food a breeze.

Using the fundamentals of the user centered design process, our team of four created an application specifically designed to make food delivery driver's jobs easier and more efficient. By focusing what our user from the beginning, their pain points, commonalities, current tools, desires, we were able to create a unique product that was built specifically for food delivery drivers. Unique features include efficient routing, notes for drop-off locations, and a variety of input methods for orders. You can view the project and all of our deliverables at delivereaseapp.weebly.com.

Competitor Analysis

Before you can understand what your users need, you need to evaluate what they already have. This is where competitor analysis comes into play. I researched one of the only main delivery driver apps currently on the market, DeliveryDroid (Left). After reading through all of the reviews on the app online (over 200 at time of project) and reading other reviews online, I compiled what current users found to be helpful and their pain points.

Retrieved from http://lh5.ggpht.com

Interviews

 Using the research collected in the analysis of existing products, thoughtful interview questions could be prepared. I interviewed a delivery driver who had only been driving for a few months. I collected pertinent data such as mode of transportation, time on the job, current technology used on the job, and current pain points. I constructed open-ended questions to reduce my bias as the interviewer. Key characteristics from our research were recorded and organized into categories.

Personas

Using this information, we began brainstorming ideas in a variety of persona areas. Thinking of our personas as real people helped us imagine the contexts in which our product would be used and how it would solve the needs and desires we had identified previously. Our records of interviews were essential in this aspect, allowing us to observe how our users defined and described their daily work flows, job responsibilities and paint points. Context scenarios helped us start to think about our app’s key paths, and how these could best be designed to aid the user in achieving their goals.
Our research led us to two main personas: a driver and a bike courier. The needs of these users very greatly, so we decided to focus on the larger user base–the drivers–due to time constraints. The driver persona is shown below.

Storyboards

Our next step was to take the design sketches and key paths and develop storyboards. Storyboards all us to envision how a user would go through potential scenarios and key paths within the application.

Scenario One

When making a pizza delivery, the driver encounters an aggressive dog. Noting this in the application warns other drivers delivering to this address, so they can adjust accordingly. This storyboard was sketched to quickly convey the users' perspective.
Adding Notes
to Customer
​Addresses
The driver rings the doorbell at the customer's address to deliver the pizza.
When the customer answers the door, the driver sees the customer has an aggressive dog. 
Thinking of one of his co-workers that is terrified of dogs, the driver decides to take note of it. When the order summary pops up, he presses the plus button to add the information.
After he finishes writing the note, he presses the check mark to confirm his submission and make it visible to other users.
Knowing he helped keep his co-workers up-to-date, the driver happily returns to his car to make the next delivery. 

Scenario Two

To aid in the input of overwhelming orders, the delivery driver uses the application's picture parsing feature. After confirmation, the delivery addresses are added to the GPS and an optimal route is created. Although storyboarding with pictures takes a little longer than sketching, it allows designers to understand how a user may interact with the application in the given scenario more easily.
Adding Order Information Using Picture Parsing
The driver comes into work and is overwhelmed by the number of orders.
The driver pulls out DeliverEase and seamlessly begins to add each order's information by taking pictures of the order slips.
After the driver takes a picture of an order form, the app scans for the order address and shows this information on the screen.
The driver clicks the check mark at the bottom of the screen to confirm the order information, adding the address to his delivery route. 
Quickly scanning the order forms allows the driver to leave with the deliveries  sooner, increasing the amount of deliveries he can make in a night.

Information Architecture

After researching the target audience and imagining how they will interact with the application based on this research, we began creating something tangible. Knowing that our personas want an application that is quick and easy to use due to time constraints on the job, influenced our decision to avoid a deep sitemap, allowing every function accessible within a few clicks. The sitemap shows how all of the web pages are connected and how the user can move between them. This assignment shaped our prototypes, wireframes, and high fidelity mockups design as well because it showed what was most important.

User Testing

Testing with the paper prototype highlighted flaws within our key paths and confusion in our layout. The paper prototype, being such low fidelity, allowed our team to make quick edits and retest until our key path flow worked as desired. Someone outside of our team tested our key paths and design choices using our paper prototypes.

Annotated Wireframes

Wireframes were created in the context of user research and testing, and annotations help explain layout choices so the reader is not left confused.

High Fidelity Mockups

Our high fidelity mockups represent the culmination of a quarter full of research, testing, revisions, more testing, more revision, and lots of hard work! The high fidelity mockups were creating using Sketch, using what worked with our wireframes, and improving the things that did not work as well. ​​High fidelity mockups were not created for the entire app, but rather for specific and important key paths through our product. Our research showed that the input of addresses, management of routes, and navigation data was important to our users. Our high fidelity mockups show screens for all of these goals.