Koobkooc
Reverse Cookbook
Team Members
-- Umar Bin Moiz
-- Lim Chek Jun
-- Park Jinah
-- Jerrold Tan
Figma Link :
https://www.figma.com/file/zfMqQCw1KflpqBZO6ufmBj/Kookooc-Week-13-Prototype-Template?node-id=204%3A3525
Problem
Current cooking references are not intuitive to use and often cluttered with ads and unwanted information
Home cooks are limited by space as they cannot have a lot of ingredients unlike large restaurants
Current applications usually only allow for search by dish name and are inflexible in allowing the user to filter by ingredients.
Key Statistic: 74.3% of home cooks don’t know what to cook with their ingredients.
Solution
An all-in-one mobile cooking application
Allows for searching and reverse search by filtering ingredients that the user hasIncludes a social platform to share and browse recipesLightweight design (convenient to open and use right away)
User Study
User Study Method
Questionnaire We did a questionnaire to acquire a general understanding of our target audience
InterviewNext, we picked a few test subjects to be subjected to intense questioning by our bipartisan committee of approved User Research Process Researchers.
Findings
We found that our methodology for our qualitative and quantitative analysis have given rise to conflicting results that we have to resolve, especially the questions regarding supplementary features which users want. We decided to thread carefully and disregard the quantitative portion of our user research on supplementary features and solely rely on our small but in depth interviews with our target audience to understand what users want in addition to the primary feature of the product. Gathering from these data points that we have, we created user stories of what the user wants to be able to achieve using our prototype. We then grouped these user stories into distinct groups which represent features that are short-listed to be implemented. After that, we sorted these potential features into categories such as: must have, good to have, will not have. These categories of features will guide us in what we need to put into our prototype and not suffer a severe case of featuritis. For example, we have our core main functionality of “reverse search of recipes using ingredients” in must have and an often requested function of “uploading new recipes” as good to have.
Sample Questions
Interview Feedback
Answers related to cooking references and why:
“youtube web version” because he can “find recipes and then modify to his own liking,” “easily search for content that you want,” “can find related video to the one you are watching.” ”Google webpages” because Google has “a lot of content” and “don’t have to navigate through the video bar during cooking.”
”Recipe books”
Answers related to pain points on those references:
Have poor creativity and not know what to cook even with a wide range of ingredients given existing solutionsUnable to harness the inside mum to cook something with few ingredientsContents on Google and Youtube can be published by anyone, so sometimes the recipe is not reliable (not accurate or detailed enough).There are too many contents on web pages so I cannot choose what to use. Sometimes I don’t have all the ingredients stated in the recipe.
| Features Users Wanted | Features Users did not want |
|---|---|
| Find Recipes for specific Ingredients | Storing ingredient cost and expiry dates |
| Bookmark feature | Too informative |
| Reliable recipes | Social feature |
| Ability to search for suitable and appropriate recipes | Handsfree feature |
| Irrelevant stories on top of the recipes |
Page 1/3