Eat-In
Mobile App

3 weeks to Research, Define & Ideate 1 app feature, test and deliver a hi-fi prototype. Presentation Deck Click here
Stakeholder Goal:
Create a mobile app for meal planning.
TO ACCOMPLISH THIS
RESEARCH was NEEDED
STRATEGY

INITIAL
Target User
​
--Young adult
* Independent
* Adventurous
* Friendly & Outgoing
| Has a weekly budget
| Tired of repetitive recipes
| Eat at home more
| Wants to maintain fit & healthy lifestyle
| Wants to entertain more
Research Goals:
-
Discover current meal preparation habits
-
Understand what might make meal planning easier
-
How do users' grocery shopping habits relate to cooking habits
To attain this goal we developed a 1:1 interview along with a 12 questions survey and was able to collect data over the 3 day period. After seeing the results of the survey, refinement was necessary so I iterated the survey. Due to time constraints, the data collected from this iteration was minimal and it therefore, not included in the result finding that are shown below.
User Interviews:
​
What we learned from
​
5
1:1 Interviews

Users need a quick way to find meal ideas on busy weeknights

Users need suggestions for meals based on ingredients they already have

Users need a way to know what they need to purchase at the grocery store for meals they want to cook later

75%
​
of interviewees & those surveyed have 30-60 min to cook a meal

53%
​
of those surveyed Cook 3-4 times a week

75%
​
of interviewees & those surveyed eat out because it is faster than deciding what to cook
12 Question Survey:
​
What we learned from
​
23 Responses
During Design & Ideation
we plotted the detailed interview and survey results on an Affinity Map to solidify the problem and help give us direction to developing the solution.
We further refined our solution when we used "I Like" "I wish" "what If" and an empathy map to narrow down the feature that would have the biggest benefit to the user that would be the easiest to implement.
Discoveries made
Digital Recipe Ideas
Interviewees like to cook what looks good.
​
Kitchen knowledge comes from their parents and the internet.
Premade Lists
Those interviewed typically buy one week worth of groceries at a time.
Oranized Meal Plan
85.7% of users surveyed cook dinner when they cook.
​
They cook breakfast and lunch but let frequently.
Cook from what I Have
Those interviewed care about eliminating food waste (i.e. spoilage) and are spending too much money eating out
We further applied the research data to refine our user persona, develop a storyboard, and define a typical journey for our mobile meal planning application.
. . . . . . . . . . . . . . . . . . . . . . . . .
Our Lo-Fi/Paper Prototyping was a Team Colaboration

We brought together our paper prototypes and picked the features we thought would be useful to a user. From there we developed a lo fidelity prototype to test.
User testing was conducted on these prototypes and changes were made based on our user feedback.

During our mid fidelity prototype testing we we found that color gave some clarity but even further revisions were needed.
Hi-fi prototypes

Conclusions



Project Take-a-Ways
Having clearly defined roles reduces duplication of work.
Interpretation of research date affects the direction of features developed/changed.
Additional hi-fi prototype testing is needed for additional project iterations.