Objective
Create a responsive web app that gives users a simple intuitive way to connect with an expert in any field within seconds so they feel informed and more prepared to face their everyday (and not so everyday) problems
Challenge
People need a way to gain confidence in the kitchen with cooking new things, updating old recipes and finding a way to pair food and drink together.
We will know this to be true when we see a consistent increase in the number of people using our app that gives them a way to connect to experts and a community of others to get advice on how to improve their skills in the kitchen.
Solution
To help people in the kitchen I created a way for home cooks to watch videos made by chefs walking them through recipes or how to use kitchen gadgets and cooking techniques. I also made a way for homecooyks to message experts to ask questions and get advice.
Context
This project was a part of the immersive CareerFoundry UX design course, while learning design thinking and the design process I was putting the lessons into practice with this project. The goal of this course is to go through the design process in a real life situation from start to finish.
My Role Tools
Competitive Analysis Figma
User Interviews Keynote
Wire framing Optimal Sort
Prototyping Usability Hub
Usability Testing Pencil Paper
Collaberation
User Research
User Personas
User Journey
Site Map
Card Sort
Prototypes
A/B Tests
Preference Tests
Competitive Analyses
In order to begin the project I had to learn about the landscape that my app would eventually be in. I started off by analyizing two competitor Yummly and Epicurious. I wanted to see worked well and not so well to.
Revised Research Goals
• Collect data on context in which users would use a cooking app.
• Discover how participants use previous cooking apps.
• Determine what features would be beneficial in a cooking app.
• Determine pain points of existing cooking apps.
Interview Insights
• All three participants wanted an easier way to find recipes.
• All three participants had the same complaint when it comes to not being able to find
ingredients in the store but had their one idea for a solution.
• Although all three participants said they would talk to chefs they also each had a
different reason for connecting. One wanted advice on cookware, another on easy
meal recipes and the last because they had similar taste in cuisine.
• One of the biggest pain points was that some websites recipes aren’t detailed enough
causing one of the participants to mix and match recipes when looking for something to cook.
Interviews
After the surveys I was able to revise my research goals
and come up with questions to better understand how people
would use my app during the interviews.
Affinity Map Insights
Users wanted faster way to find recipes
Users wanted faster way to shop for food
Users wanted videos that were easier to follow
Users wanted better way to introduce new food/ingredients
After gathering the my notes from the interviews I was able to create an affinity map in Figjam. Picking out statements and quotes I found important I grouped them as Behaviors/Attitudes, Wants/Needs, Frustrations, Qutoes and Cooking, Experts, Shopping, Recipes.
Using the personas and the data from the interviews I was able to map out the emotional journeys the users might have while using the app, which lead to a new phase.
User Personas
Using the data from the interviews I was able to create personas to become the face of my potential users.
Now that I had mapped out the users emotional journeys I could map out the quickest journey the users would take to complete their tasks.
• Collect data on the content in which users would use a cooking app
• Discover what cooking apps/websites potential users currently use or have used
• Identify pain points in any existing cooking apps
Survey Insights
• The majority of participants don’t use cooking apps, but would if they could connect with experts.
• 37% of participants said they would like to connect with a nutritionist.
• 55% of participants said they would want to discuss ingredient substitutions.
• 89% of participants said they would like to find recipes that use ingredients they already
have.
I now felt that I had enough information that I could build out the information architecture and create a site map that would help me define the scope of my app.
Strengths
Smart thermometer gives the option to connect without signing in
Grocery delivery service
Learns what you like
Guided cooking videos
Allows easy meal planning
Bring recipes from different sites to one place
Weakness
Some recipes send you to another site for the directions
Nutritional facts aren’t free but when sent to another site by the recipe the nutritional facts are there for free
Original recipes are not free
Video sound didn’t work in full screen
Strengths
Smart timer that adjusts to type and quantity of food
Professional demos of kitchen tools
Ingredient list includes special equipment needed
Location service to teel you what’s locally in season
Home page gives themed recipes
Free
Weakness
Videos on the app aren’t organized
Recipe ratings don’t always reflect user ratings
Recipes don’t list skill level
No nutritional info
Must open website to search videos or read articles
Using the information I recieved and getting others opinions on some asthetic changes I implemented, I was getting closer to turning my mid-fidelity prototype into a high-fidelity prototype.
Goals:
The main goal of this test is to evaluate the learnability of Eat It. I will be observing if users understand the app, its value and how to complete basic tasks such as logging in, creating and saving a shopping list, watching an experts video and messaging an expert.
Methodology:
Testing will be done both in-person and remotely, with a clickable prototype on the users phone.
Participants:
There will be 6 participants aged from 25-60 recruited from personal/social network, with interests in food and cooking.
Metrics:
Errors will be measured using Jakob Nielsen’s scale
Findings
Use more universally understood icons
Get rid of confusing extra info
Add feature to show recent or bookmarked recipes
Make search easier to use
I learned just how important it is to get the opinions of other designers on your design, they can catch things you missed. I found that some of my bright ideas weren’t as bright as I thought they were.
I originally thought it would be a good idea have the search results start big then get a little smaller based on popularity, others just thought it confusing and after thinking about it i had to agree.
I also found that making sure that a design can be used just as easily for the handicapped makes the design better for those that aren’t handicapped as well
Closing
What I Learned
How to conduct user testing
How to receive and incorporate criticism
How to evaluate test results
Surveys
I started by putting out a short survey online with google docs.
Feel free to try the prototype