My iRecipes Mobile Cooking App Concept

UX Design Process

Here’s how I used the UX design process to create a cooking app prototype for the iPhone platform.  The work was performed for the UX Design Professional Certificate at UC Berkeley.

My goals were to:

  • Find out pain points experienced by users of popular cooking apps
  • Design a cooking app flow that improved the user experienced based on my research
  • Test my ideas on usertesting.com to get feedback
  • Create a visual design and prototype
  • Recommend ways to measure success

Getting Started: Competitive Research

I was starting from a "blank slate", so I researched popular cooking apps to learn about how cooking app companies try to meet user needs.

User Research

After getting a big-picture perspective by doing competitive research, I wanted to get first-hand opinions about features and app usage.

I conducted a 10-question survey of 20 people on Survey Monkey to find out about what features they liked in a mobile cooking and app, as well as their pain points.

Key Findings

Survey results:

  • Users like to start their search with a key ingredient
  • Users want to be able to easily see recipe steps on their phone
  • Users like to validate recipes via user reviews and ratings (very important)
  • Users prefer a free ad-driven app over paying for one
  • Users are only mildly interested in generating a shopping list from the app
  • Users only mildly interested in how-to videos
  • It’s not important that users save notes within recipes

Ideation

Based on user need to start recipe search by ingredient:

  • Assumption: families like to rotate meals based on protein type - chicken, beef, pork, seafood, vegetarian, etc.
  • Idea: create information architecture and wizard-like flow that starts with a protein choice, and then by cooking method, recommended cut, and flavor profile to narrow down search and not return too many results

Based on user need to view recipe on phone:

  • Observation: most cooking apps require a lot of scrolling to go back and forth between steps and ingredients and small type size can be hard to read
  • Idea: create information architecture that presents recipe steps with horizontal swipe rather than vertical scrolling
  • Idea: create information architecture that has easy toggle between steps and ingredients

Customer Journey

Based on my research, I now had an idea of a user flow that I wanted to mockup and prototype. Here I created a customer journey - a visualization of a process that a user may go through to accomplish a goal and pain points experienced along the way.

Persona

I created a persona to really understand who I was designing for.  It was important to understand their goals and frustrations so that my app design would provide solutions for them.

User Stories

User stories were written for the UX team to articulate how a piece of work will deliver a particular value back to the customer.

Navigation Map

A navigation map was created to outline and organize how the user would go from screen to screen in a full app design.

Lo-fi Paper Prototype

The Guided Search feature lets the user pick from a series of choices - protein, cooking method, cut, and flavor profile in a wizard format to better narrow their search results.

In-person tester feedback

  • Home screen too busy
  • Apple "picker" seemed dated

Testing a Wireframe Prototype

I conducted a remote, unmoderated test using Sketch/Invision on Usertesting.com.  There were eight testers.

Feedback for guided search:

  • Flow makes sense
  • Good categories to have (protein, cooking method, cut, flavor profile)
  • Doesn’t like “cut” as a search criteria choice
  • Change flavor profile to cuisine

Feedback for improved readability of recipe while preparing a meal:

  • Good to have shortcut to ingredients
  • Great to have no scrolling of steps - easy to keep your find your place in recipes
  • Awesome to toggle to ingredients and back to steps
  • Interesting concept

Next Steps: Measuring Success

Initial tester feedback about the proposed features was generally positive. However, more metrics are needed to measure the success of these ideas.

Task Success Rate: do quantitative research to measure the percentage of participants that successfully complete the Guided Search steps to view a recipe and save it to the cookbook. Also, measure task success of feature vs. other search methods, such as browsing, key word search, and search by cuisine.

Customer Satisfaction (CSAT):  do more qualitative research to find out how well features aid completion of planning and preparation goals.