Leftovers - App design

Mobile app design for one of Canada's biggest food rescue non-profit organization.

Mobile application for people who want to donate their extra backyard harvest

Leftovers Redesign - Mobile App

Overview

Leftovers is a Canadian non-profit organization and its' mission is to reduce food waste and increase access to the food for people in need. They work with volunteers, donors, and service agencies across Canada to rescue and redirect food.

Role

Product Designer

User Research, Visual Design, Prototyping & Testing

Tools

Figma, InVision, Miro, GitHub, VS Code

Project time

3 weeks

My Process:    1. Research & Discover    2. Define & Ideate    3. Prototyping & Testing

1. RESEARCH & DISCOVER

USER RESEARCH AND UNDERSTANDING THE PROBLEM

10 user tests over the phone & 22 user surveys

When we first started the user research process, we had two goals in our mind: 1. run user tests on the current Leftovers website and 2. conduct user surveys to find out if people (who grow their harvest) would be interested in using an app to donate their excess food.

My team and I created a Google survey with 10 questions and 22 participants completed the survey. Some questions we had on the survey included the following:

  1. How much more food do you grow than you can use (i.e. is there food waste)?
  2. What do you usually do with your excess harvest?
  3. Would you be willing to donate the excess if you had the opportunity?
  4. How comfortable would you be using an app to donate food? (1 = very uncomfortable and 5 = very comfortable?)

Some of the Google survey results

We also ran 10 user tests on Leftover's current website to discover the biggest pain points for the users and to understand how to create a better user flow for our Leftovers app design. When we ran the usability test, we concentrated on two different scenarios:

Scenario 1:

You are a local farmer that grows beets and carrots. Sometimes the vegetables you harvest have imperfections and they are not acceptable for sale, but are perfectly fine to eat. You don’t want to waste good food and are willing to donate a few boxes of “imperfect” vegetables from your harvest. You decide to explore their service. Please follow these prompts:

  1. Look at the homepage without scrolling. What does this organisation do?
  2. Now scroll through the homepage. Describe what you think this organisation does.
  3. Take some time to explore the website and describe what you see. Talk about what you like and what you’re unsure about.
  4. Go back to the homepage. If you wanted to donate your vegetables, what steps would you take on this website?
  5. How was your experience finding the food donation area? Could it be improved in any way?

Scenario 2:

You have an apple tree that produces a lot of apples every year and it produces more than you can use. 

You decide you want to donate extra apples to an organisation. You find Leftovers website and decide to explore their service.

  1. Search for where you would donate your harvest to.
  2. If you choose to donate money to the organisation how would you perform that task on the site?

Based on the data gathered from the survey, we discovered that:

  • Individuals who grow food on their backyard, almost always waste some of it.
  • Individuals try to give the extra harvest to friends and family.
  • Some of the extra harvest will get bad and is wasted every year.
  • 91% of people who grow their own food would be willing to donate their excess harvest.
  • 63% felt positively or neutral about using an app to book their donation.
  • 86% were not familiar with "food rescue" organizations.

Based on the data gathered from the user tests on the current website, we discovered that:

  • Users found that the purpose of the current website was unclear.
  • The donation process was confusing and the website was hard to navigate through.
  • Too much scrolling to find what a user needs.
  • Website's layout and graphics are not appealing.
  • Call to action unclear.

Problem

  1. People often have extra harvest but don't know how to donate it.
  2. During the qualitative research, we discovered that the Leftovers Foundation website was difficult to navigate and it was hard for users to make a food donation.

Solution

My team and I wanted to create a mobile app for Leftovers with clear step by step instructions how to contribute and simplify the process of donating extra harvest by funneling users into a right user flow and improved information architecture.

2. DEFINE & SYNTHESIZE

EMPHAZIGING THE USER

After the user research, we created an user persona based on the findings from the user research:

User Persona Anna

Motivations:

  • Donate the apples that would otherwise go to waste.

Pain Points:

  • It's time-consuming to pick all the apples yourself.
  • Not aware of how to donate excess apples.

Based on these findings, my team and I decided to concentrate on one user flow (how a user can donate their extra apple harvest).

IDEATING

As a starting point, we did some market research on competitors to investigate what kind of food rescue companies are currently out there. We conducted a heuristic evaluation and SWOT analysis for each competitor and gathered the strengths we would want to apply to our mobile app.

Second Harvest - Canadian food rescue company

  • Clean navigation
  • Consistent Icons

Not Far from the Tree - Toronto fruit picking and sharing service

  • Clear purpose
  • Clear User Flow

Rescuing Leftover Cuisine - food rescue Organisation in the USA

  • Clear steps to donate food


After the Competitor analysis was done, we started to create a User Journey. We had already previously decided to concentrate on a user journey for someone who wants to donate their extra apples to a charity. Since we had discovered from our user research, that for most of the users, it's hard to navigate through the website, we wanted to ensure a smooth navigation for our app design.

User Journey Map

From the User Journey, we moved on to deciding which features and things we want to concentrate on. My team and I had a brainstorming session and as a result, created a Priority Matrix to help us to design the mobile app.

Priority Matrix

During the brainstorm session, we also referred back to our user research results and decided to concentrate on four different things when designing the app:

  1. The purpose of the app must be clear.
  2. Clear call to action buttons.
  3. Clear User Flow.
  4. Clean and minimalistic design.

USER FLOW

We wanted to concentrate on creating clear user flow for donating backyard harvest. Based on the user research, we had discovered that donating process was confusing and since donating food is one of the main tasks you can complete on Leftovers' website, we wanted to ensure that user flow is clear on our App.

User Flow for donating backyard harvest

NOTE ABOUT THE COLORS - WCAG GUIDELINES

We also wanted to make sure that our app design would pass WCAG guidelines - during our user research, we noticed that the current Leftovers website didn't pass WCAG's color guidelines so we considered that when designing the colors for the app.

PROTOTYPING

LOW-FI

After the ideating phase, we started to work on our first sketches - our main focus for the landing page, was to ensure that the call-to-action buttons and the purpose of the app is clear to the users.

Low-Fi Landing Page

MID-FI

After creating a few quick sketches, we started to work on a Mid-Fi prototype and made them clickable so we could run some user tests on them and iterate further.

TESTING AND ITERATING

Because of time constraints, we moved quickly to our Hi-Fi prototype. We focused on prototyping the Backyard Harvest donation flow and we added step-by-step instructions to address the confusion that our users felt about the process on Leftovers’ original website. Finally, we spread out the donation form across 5 pages to reduce scroll and added indicators to show which step users were on in the process. We performed usability testing with 5 users. All of our users were able to easily complete the Backyard Harvest donation process, but we did receive feedback that our color scheme and design could be more related to food and harvest.

Mid-Fi Prototype

HI-FI

For the Hi-Fi version, we changed the color scheme as per the feedback we had received from the user testing for the Mid-Fi prototypes. We also ensured all the colors followed the WCAG guidelines and are accessible to all the users. We also didn't want to use white (#FFFFFF) for the background or completely black (#000000) for the fonts to avoid too big of a strain on an eye.

Hi-FI Prototype



FINAL THOUGHTS

We would want to spend time with the stakeholders to review the current site content and perform analytics and based on those findings, we'd improve the user flows and design new features. My team and I find it important to minimize the number of clicks from the home page to important content and make navigation easier. In the future, we'd perform more user tests and make changes based on those findings.