UX Designer & Researcher
UX Project - App
Cookeat
Project Overview
In a user experience course, we designed an app for cooks. From searching and choosing the desired recipe to cooking, the product helps the cook. It uses speed, simplicity and reliability. Analyzing information to build personas and information architecture was part of the tasks. Finally, building wireframes and prototyping.
Understanding The Problem
Before we started writing the survey, we asked what insights we were looking for?
1. Who is our target audience?
2. How often do they cook?
3. How often are recipes used?
4. Where do they get the recipes?
5. Is there any difficulty finding a suitable recipe? If you had difficulty, what was the difficulty? And what was the solution?
​
With these goals in mind, we constructed the questionnaire, as well as interviewed some of the people who answered it.
Product Goals
Digital Space
To create a digital space where it is easy to find reliable, varied and user-friendly recipes. By maintaining a uniform and simple language structure.
A Smooth Experience
An entire cooking process, a recipe from selection to bite. The application is based on speed, simplicity, and reliability values.
Making It Easy
By understanding the pain points of users, we offer solutions to problems that go unanswered. As well as a personalized experience tailored to the user's wants and needs.
Competitor Research
Our competitors' research focused on 3 of the world's leading cooking platforms.
Pros:
-
Comprehensible cooking format
-
Interface providing reliable recipes to website users
-
Filter recipes by categories (preparation time, type of meal)
-
Preparing the recipe according to the number of diners
Cons:
-
A high cognitive load may occur in users due to the website's visibility
-
Long recipe pages cause excessive scrolling for users
-
No step-by-step recipe prep checklist
-
It is not possible to follow other chefs
Reaserch Insight
User Current Experience
-
The users usually cook almost every day or once a week
-
The popularity of a recipe (comments, bloggers, rating) influence the choice of the recipe
-
Occasionally in searching and finding the recipe there were on subtitutes for changing the recipe components
-
The cooking is almost always planed in advance
-
The most common platform where users search for recipes: Google, family and friends and blogs.
User Difficulties:
-
There were too many recipe option for every kind of dish- Hick's law
-
They looked for inspiration on what to cook and were unsuccessful in deciding what to cook
-
There were no ratings and comments that indicated the reliability and quality of the recipe
-
Substitutes for ingredients were no listed
Summary Of Pain Points:
1. The user wants to cook, but does not know what and how
2. Recipes that are scattered throughout the network
3. The reliability of the recipe found online (rating, comments, who wrote the recipe)
4. There is not always a convenient interface that accompanies the cooking itself
5. There is not enough detail on the quantities of products that came out of the recipe
6. There are not always alternatives for vegans, vegetarians and kosher
User Profile:
The Main User Scenario:
Information Architecture:
Wireframes:
