Receta: Cooking assistance and social connection application
Receta:
A cooking assistance
& social connection application.
Receta: Cooking assistance and social connection application
Role
UX/UI Designer/Researcher
Approach
Culinary
Duration
2 months
Medium
Food and Hospitality
Your Recipe orgnization, Your connectivity, and Your way
Project Overview
Receta is an all-inclusive recipe import and organization prototype. Our application allows users
to add recipes online or other application with ease. In addition, their is a social forum which is
utilized to allow users to connect with other chefs for culinary advice. The idea was pitch by our
team leader Datsayna Medina at Kennesaw State University.
Research Phase
View Prototype here
View Prototype here
Research Phase
Bleak Organization, lack of user cooking assistance, and lack of user freedom
The Problem
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Feature / Feedback |
|---|
Recipe Keeper |
|---|
Anylist |
|---|
Paprika
Import recipes from web/URL
✓
✗
✓
Copy/paste/cross-list ingredients
✗
✗ |
|---|
✗
Multiple users/sync family devices
✗
✓ |
|---|
✓
Calendar/meal planning
✗
✗
✓
Recipe scaling
✗
✗
✓
Ingredient unit scaling
(auto change oz to cups, etc.)
✗
✗
✗
Subscription required for full features
✗
✓ |
|---|
✗
Undo/redo for |
|---|
✗
✗
✗
Modern UI/graphics
✗
✓ |
|---|
✓ |
|---|
Onboarding/clarity of clickable areas
✗
✓ |
|---|
✗
Accessibility options (text size, highlighting, etc.)
✗
✗ |
|---|
✗
Save recipes for future reuse
✓ |
|---|
✗ |
|---|
✓ |
|---|
Add notes to imported recipes
✓ |
|---|
✗ |
|---|
✗
Customizable cookbook export (PDF/print)
✓ |
|---|
✗ |
|---|
✗
Preset recipes/tutorial for new users
✓ |
|---|
✗ |
|---|
✗
Your Recipe orgnization, Your connectivity, and Your way
Project Overview
Receta is an all-inclusive recipe import and organization prototype. Our application allows users
to add recipes online or other application with ease. In addition, their is a social forum which is
utilized to allow users to connect with other chefs for culinary advice. The idea was pitch by our
team leader Datsayna Medina at Kennesaw State University.
Laying our foundation
Problem Statement
This is where we define our problem to guide our research. Problem Statement: The current state of cooking/recipe applications has focused primarily on cooking blogs. What existing products/services fail to address is convenience, ability to pull from different sources, and user social interaction. Our product/service will address this gap by providing a fun and unique user interface for cooks to connect, find inspiration, and create their own personalized recipe books.
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Feature / Feedback |
|---|
Recipe Keeper |
|---|
Anylist |
|---|
Paprika
Import recipes from web/URL
✓
✗
✓
Copy/paste/cross-list ingredients
✗
✗ |
|---|
✗
Multiple users/sync family devices
✗
✓ |
|---|
✓
Calendar/meal planning
✗
✗
✓
Recipe scaling
✗
✗
✓
Ingredient unit scaling
(auto change oz to cups, etc.)
✗
✗
✗
Subscription required for full features
✗
✓ |
|---|
✗
Undo/redo for |
|---|
✗
✗
✗
Modern UI/graphics
✗
✓ |
|---|
✓ |
|---|
Onboarding/clarity of clickable areas
✗
✓ |
|---|
✗
Accessibility options (text size, highlighting, etc.)
✗
✗ |
|---|
✗
Save recipes for future reuse
✓ |
|---|
✗ |
|---|
✓ |
|---|
Add notes to imported recipes
✓ |
|---|
✗ |
|---|
✗
Customizable cookbook export (PDF/print)
✓ |
|---|
✗ |
|---|
✗
Preset recipes/tutorial for new users
✓ |
|---|
✗ |
|---|
✗
Hypothesis on user wants and goals
Persona Hypothesis
Through our own fine-tuning we broke town the user goals and behaviors. We concluded that most users should be beginners to cooking and need moderate recipe assistance. However, there is a second option for intermediate users who would require fine-tuning previously made recipes and customizations. With this information, we conclude that beginner users would need basic and simple features, while intermediates should be interested in more in-depth features such as social connection.
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Feature / Feedback |
|---|
Recipe Keeper |
|---|
Anylist |
|---|
Paprika
Import recipes from web/URL
✓
✗
✓
Copy/paste/cross-list ingredients
✗
✗ |
|---|
✗
Multiple users/sync family devices
✗
✓ |
|---|
✓
Calendar/meal planning
✗
✗
✓
Recipe scaling
✗
✗
✓
Ingredient unit scaling
(auto change oz to cups, etc.)
✗
✗
✗
Subscription required for full features
✗
✓ |
|---|
✗
Undo/redo for |
|---|
✗
✗
✗
Modern UI/graphics
✗
✓ |
|---|
✓ |
|---|
Onboarding/clarity of clickable areas
✗
✓ |
|---|
✗
Accessibility options (text size, highlighting, etc.)
✗
✗ |
|---|
✗
Save recipes for future reuse
✓ |
|---|
✗ |
|---|
✓ |
|---|
Add notes to imported recipes
✓ |
|---|
✗ |
|---|
✗
Customizable cookbook export (PDF/print)
✓ |
|---|
✗ |
|---|
✗
Preset recipes/tutorial for new users
✓ |
|---|
✗ |
|---|
✗
Persona Hypothesis
How many roles will your app have? (Roles are distinct - dog walker vs. walkee, Esty seller vs Esty buyer)
There is one user role - users importing recipes
What different sorts of people might use this product - break down by role (if 2 roles, two separate paragraphs)?
Beginner - Importing and access
Beginners are freshly new to the experience of cooking. They are coming in with little to no foundational knowledge. They are looking to build a relationship with cooking.
Intermediate - Customization and fine tuning
Intermediate to advanced users are more familiar with the foundations of cooking and recipe building. They use recipes more as a guideline rather than by the book. They are looking to fine-tune or strengthen their cooking skills.
How might the needs and behaviors vary?
Beginner users might use more of the basic and simple features. Beginner cooks should have easy access of importing recipes via camera, webpage, PDF. They would want the convenience of accessing any recipes they want to try from one single interface. They would look for more basic/essential cooking tips.
Intermediate cooks would be interested in the more in-depth features of the app. They would use the same basic features, but are more likely to look for niche spaces and recipes, using more customization tools and looking for advanced recipes as well.
What ranges of behavior and types of environments need to be explored?
What specific tools are beginner and intermediate users using differently?
How much control might an intermediate user want over a beginner user?
How might home cooks and industrial cooks vary, especially in terms of how/when they would use the app?
What types of features are most commonly shared between beginner and intermediate users?
Persona Hypothesis
How many roles will your app have? (Roles are distinct - dog walker vs. walkee, Esty seller vs Esty buyer)
There is one user role - users importing recipes
What different sorts of people might use this product - break down by role (if 2 roles, two separate paragraphs)?
Beginner - Importing and access
Beginners are freshly new to the experience of cooking. They are coming in with little to no foundational knowledge. They are looking to build a relationship with cooking.
Intermediate - Customization and fine tuning
Intermediate to advanced users are more familiar with the foundations of cooking and recipe building. They use recipes more as a guideline rather than by the book. They are looking to fine-tune or strengthen their cooking skills.
How might the needs and behaviors vary?
Beginner users might use more of the basic and simple features. Beginner cooks should have easy access of importing recipes via camera, webpage, PDF. They would want the convenience of accessing any recipes they want to try from one single interface. They would look for more basic/essential cooking tips.
Intermediate cooks would be interested in the more in-depth features of the app. They would use the same basic features, but are more likely to look for niche spaces and recipes, using more customization tools and looking for advanced recipes as well.
What ranges of behavior and types of environments need to be explored?
What specific tools are beginner and intermediate users using differently?
How much control might an intermediate user want over a beginner user?
How might home cooks and industrial cooks vary, especially in terms of how/when they would use the app?
What types of features are most commonly shared between beginner and intermediate users?
Persona Hypothesis
How many roles will your app have? (Roles are distinct - dog walker vs. walkee, Esty seller vs Esty buyer)
There is one user role - users importing recipes
What different sorts of people might use this product - break down by role (if 2 roles, two separate paragraphs)?
Beginner - Importing and access
Beginners are freshly new to the experience of cooking. They are coming in with little to no foundational knowledge. They are looking to build a relationship with cooking.
Intermediate - Customization and fine tuning
Intermediate to advanced users are more familiar with the foundations of cooking and recipe building. They use recipes more as a guideline rather than by the book. They are looking to fine-tune or strengthen their cooking skills.
How might the needs and behaviors vary?
Beginner users might use more of the basic and simple features. Beginner cooks should have easy access of importing recipes via camera, webpage, PDF. They would want the convenience of accessing any recipes they want to try from one single interface. They would look for more basic/essential cooking tips.
Intermediate cooks would be interested in the more in-depth features of the app. They would use the same basic features, but are more likely to look for niche spaces and recipes, using more customization tools and looking for advanced recipes as well.
What ranges of behavior and types of environments need to be explored?
What specific tools are beginner and intermediate users using differently?
How much control might an intermediate user want over a beginner user?
How might home cooks and industrial cooks vary, especially in terms of how/when they would use the app?
What types of features are most commonly shared between beginner and intermediate users?
Used a variety of chefs with various skill level
User Research Interviews
We used our persona hypothesis as a framework for who we would recruit. Since our application can be used by a variety of users we needed to replicate this in our interviews. We selected 5 participants with a variety of cooking skills from pure beginner to experienced expert. We noticed that the beginner's main claims were the need fo cooking help and the experts just need a way to organize and share ideas. However, it really wasn;t until the experienced cooks had a goal of conveniently sharing recipes with others.
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Modeling and Requirements
Tracking our data and sorting it
Affinity Mapping
Within our interview process, we observed certain traits in our participants. Some we passionate about cooking other were just looking for an easy solution for their cooking routines. However, each person told a unique story. Based on each quality and trait we create affinity maps to map each interviewee's habits, information, challenges, wants, and needs. This data was utilized to form our user personas.
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
What most recipe assistat apps lack
Social Group Chef Threads
During our interviews multiple user asked if they could have a feature to directly connect with other chefs for help. With Receta groups and chats this helps bridge the gap between chefs from all different backgrounds.
Modeling and
Requirements
It all comes down to this
Final Iterations and flows
After gathering our data from our usability test, we saw that our users had some issues with navigation. So we utilized our featured recordings of the test to see potential gaps in our designs and fixed and debugged them accordingly. Based on the participant's feedback and decision,s we concluded with the following design iterations.
Kevin Landry Expectations
Bianca Frank Expectations
Kevin Landry Expectations
Bianca Frank Expectations
Frameworks / Wireframing Phase
The Main Key path
Cook Book Flow
The main key path of adding a recipe to your cookbook via importing. This feature allows you to organize and sort your recipes in one place. This feature enables the extra extraneous information on recipe webpages and Receta gives you the important information such as recipes and steps
View Figma Canvas
AI is moving fast
AI live recipe assistance
One of our team members suggested a live AI help feature for recipes. This was also suggested within our usability test. Thus, we went back to the drawing board add added a user friendly and easy to locate AI Receta help bot. However, we should have changed the AI graphic to make it look more distinguished.
AI live recipe assistance
AI is moving fast
One of our team members suggested a live AI help feature for recipes. This was also suggested within our usability test. Thus, we went back to the drawing board add added a user friendly and easy to locate AI Receta help bot. However, we should have changed the AI graphic to make it look more distinguished.
What did we discovered?
Observations
None of our participants were 100% confident in their cooking abilities
3 out of 5 participants see cooking as a way of self pride
Each person values simplicity and organization
Each person is open to learning new things every day
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
I need help with...
Hey, this is Gizmo, your personal cooking companion! Ask me for tips, suggestions, or help on a cooking technique you’re struggling and I’ll recommend you one of our many useful video lessons!
Social
Personal
Receta
9:41
Receta: Your Recipes, Your Way
Final Prototype
From all our data collected from the market research, competitive audit, usability test, and other important metrics. We present to you Receta: The all-inclusive recipe organization and cooking assistant application. Disclamier: Still a working prototype.
Vegan’s Only
I made pestooooo
@TBGProd58
5m
Brycee
idk what i’m doing lol 🙃
30m
Beginners
Guys idk what I’d do without my air fryer
@Mona_liSa
2hr
Vivienne
Yeah it really helped me learn the ropes
1d
Stells
fr
4d
Start a new chat
My Chats
Groups
Chat
Search
Profile
Social
Personal
Receta
9:41
Modeling and Requirements
Nothing is ever perfect, however everything requires progress
Final Reflection on the Project
For my first time working with an IAD team I can say it was a great time. We all bonded on a great level and it was simple to generate ideas. In addition, our scheduling was great we did need to spend many hours on our designs, but it was worth it. From research, wireframing, and communicating it was a good flow. Lastly, I want to pay my respects to my team Datsayana Medina, Anna Kahle, and Amanda Wallace for guiding me and providing the help the team needed.
View Prototype here
View Prototype here
Groups
Chat
Search
Profile
Dinner for Two
Group dedicated to meals for childless couples
Help, I Can’t Cook!
Meals to help you impress any person in your life, no matter your skill level
Similar Groups
Are you looking for meals to share and enjoy with loved one?
Welcome to Friendly Eats, where we help each other make bomb food 🌏
Rules:
Trolling = banned
Be unique
Be yourself
Have fun!
Join Group
360 Members
89 Posts
Friendly Eats
Social
Personal
Receta
9:41
Behavioral Variables and Curation
Persona Creation
Based on our main observations, we developed behavior variables for each participant to find common patterns. These patterns were utilized to show and identify certain opinions on certain topics and goals. We discovered a strong and identifiable divisions between the beginner cooks vs the experienced cooks. Here we were able to determine that our prototype needed to enhance user freedom and social connectivity. Red represents experienced cooks while green is beginner
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
The people who we are designing for
Personas
Here are our personas: Bianca Frank, our primary persona that represents the common user in our prototype. Bianca is a small college student that is looking towards utilizing Receta to teach her simple and easy cooking techniques to fit with her diet. Kevin Landry, our secondary persona, he represents a rather more social user that is more familiar within the kitchen. His goal is to utilize receta to learn from other chefs and connect with others in his community.
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Goals for establishing Goal-Directed Design
Persona Needs and Expectations
Here the team collectivly relized that our problem statement needed to change. We made the executive decision to add more in-depth information in our problem statement. "The current state of cooking/recipe applications has focused primarily on recipe importation and organization. What existing products/services fail to address is the ability to pull from different sources including video formats, education on cooking basics, and user social interaction. Our product/service will address this gap by providing a fun and unique user interface for cooks to create their own personalized recipe books, learn basic cooking essentials, connect, and find inspiration." Our problem statement helped us establish our persona expectations. We covered on requirements relating to communications, skill learnability, organization, and simplicity. Both personas share similar beginning and end goal, however it is the in between in where the requirements differ
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Bianca Frank Expectations
Kevin Landry Expectations
Frameworks/Wireframing Phase
Final Iterations
and flows
After gathering our data from our usability test, we saw that our users had some issues with navigation. So we utilized our featured recordings of the test to see potential gaps in our designs and fixed and debugged them accordingly. Based on the participant's feedback and decision,s we concluded with the following design iterations.
It all comes down to this
Cook Book Flow
The main key path of adding a recipe to your cookbook via importing. This feature allows you to organize and sort your recipes in one place. This feature enables the extra extraneous information on recipe webpages and Receta gives you the important information such as recipes and steps
From Low to HI
Designs
After our personas and requirements were established, it is time to move into bringing those goals to life. The team collectively utilized the Figjam cloud-based software to visualize and design key paths and validation scenarios for both user types. The validation path is labeled in magenta and the key path in green.
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Energy goes where energy flows
Prototyping
The sample above is not our full wireframe set. The full set is located on our Figjam. We based most of our designs from the wireframe above, however we did not account for the changes and extensiveness with our fine-tuning. We delegated a task of each individual to create 12-15 screens in Hi-Fidelity. However, this caused a little bit of inconsistency. Since we worked on the screens individually our UI was not universal. Later on, we all got together and made the adjustments accordingly. Utlizing a clean and simple aesthetic with a 50s color theme. In addition, we expanded on the used of an 8 pt grid for simple GUI programming, font styles, and text styles
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
View Figma Canvas
Refining our flow and interactions based on past users
Usability Testing
Although we went through our designs many times. The designer is the one who fully knows the inside and outside of a prototype. However, we needed to see if our designs were simple to navigate and matched our users' goals. To gather evidence on how usable our application was, we conducted multiple usability tests with our past interviewees.
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
It all comes down to this
Final Iterations and flows
After gathering our data from our usability test, we saw that our users had some issues with navigation. So we utilized our featured recordings of the test to see potential gaps in our designs and fixed and debugged them accordingly. Based on the participant's feedback and decision,s we concluded with the following design iterations.
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
The Main Key path
Cook Book Flow
The main key path of adding a recipe to your cookbook via importing. This feature allows you to organize and sort your recipes in one place. This feature enables the extra extraneous information on recipe webpages and Receta gives you the important information such as recipes and steps
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Easy Meals
Salmon with Brown
Sugar Glaze
Emily Weinberger
Published: 4/23/24
Uploaded from: Simply Recipes
Uploaded to Receta: 5/15/24
Homemade Baked Lasagna
Brandie
Published: 3/27/21
Uploaded from: The Country Cook
Uploaded to Receta: 1/23/24
Sheet Pan Sausage,
Peppers, and Onions
Sheela Prakash
Published: 6/7/24
Uploaded from: Simply Recipes
Uploaded to Receta: 2/2/25
To Die For Fettucine Alfredo
Erin Marie
Published: 2/12/18
Uploaded from: AllRecipes
Uploaded to Receta: 3/12/25
Stuffed Peppers
Rian Handler
Published: 12/9/24
Uploaded from: Delish
Uploaded to Receta: 3/23/25
Chicken Nuggets
Jose.elCook
Published: 3/20/25
Uploaded from: Files
Uploaded to Receta: 4/24/25
Favorites
Lazy Pasta
FitGreenMind
Published: 3/28/24
Uploaded from: YouTube
Uploaded to Receta: 1/23/24
Bibimbap
Kay Chun
Published: 4/13/22
Uploaded from: Bon Appetite
Uploaded to Receta: 7/18/24
Broccoli Beef Ramen
Stir Fry
Nick Evens
Published: 11/4/24
Uploaded from: Simply Recipes
Uploaded to Receta: 3/14/25
Ranch Chicken Crockpot
(Crack Chicken)
Valentina Ablaev
Published: 8/20/22
Uploaded from: Valentina’s Corner
Uploaded to Receta: 4/24/25
Healthy Sides
Jicama Salad
Elise Bauer
Published: 1/10/24
Uploaded from: Simply Recipes
Uploaded to Receta: 4/14/25
Spicy Cucumber Salad
careesekwok
Published: 2/20/25
Uploaded from: TikTok
Uploaded to Receta: 3/16/25
Desserts
Soft and Chewy Sugar
Cookies
Tessa Arias
Published: 9/30/21
Uploaded from: Handle the Heat
Uploaded to Receta: 3/15/25
Grandma’s Cookies
Grandma
Published: Sometime in the 90’s
Uploaded from: Files
Uploaded to Receta: 4/10/25
Bianca’s Cookbook
Cookbook
Prep
Import
List
Help
Social
Personal
Receta
9:41
Ranch Chicken Crockpot (Crack Chicken)
Category:
Select Category
Valentina Ablaev | Valentina’s Corner | Published: September 20, 2022 | Uploaded to Receta: April 24, 2025
Ingredients
Serving Size:
4 servings
2 lb
boneless skinless breast
2
garlic cloves minced
2 Tbsp
ranch powder
3 Tbsp
unsalted butter
1/4 cup
chicken broth
1/2 tsp
salt
1/4 tsp
ground black pepper
8 oz
bacon chopped and cooked
1 1/2 cups
shredded cheese
12 oz
cream cheese room temp
Steps
1.
Add the chicken breast, cream cheese, minced garlic, ranch powder, butter, chicken broth, salt, and black pepper into the crockpot.
2.
Close the lid and cook on high for 3-4 hours or on low for 6-7 hours.
3.
Remove the chicken and using two forks, shred the chicken breast.
4.
Add the shredded chicken, cooked bacon and shredded cheese back into the crockpot and mix. Cook just until the cheese melts.
5.
Serve as desired and enjoy!
Additional Notes:
Save
Cookbook
Prep
Import
List
Help
Social
Personal
Receta
9:41
Social Group Chef
Threads
What most recipe
assistant apps lack
During our interviews multiple user asked if they could have a feature to directly connect with other chefs for help. With Receta groups and chats this helps bridge the gap between chefs from all different backgrounds.
Final Prototype
Receta: Your Recipes,
Your Way
From all our data collected from the market research, competitive audit, usability test, and other important metrics. We present to you Receta: The all-inclusive recipe organization and cooking assistant application. Disclamier: Still a working prototype.
AI is moving fast
AI live recipe assistance
One of our team members suggested a live AI help feature for recipes. This was also suggested within our usability test. Thus, we went back to the drawing board add added a user friendly and easy to locate AI Receta help bot. However, we should have changed the AI graphic to make it look more distinguished.
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Nothing is ever perfect
For my first time working with an IAD team I can say it was a great time. We all bonded on a great level and it was simple to generate ideas. In addition, our scheduling was great we did need to spend many hours on our designs, but it was worth it. From research, wireframing, and communicating it was a good flow. Lastly, I want to pay my respects to my team Datsayana Medina, Anna Kahle, and Amanda Wallace for guiding me and providing the help the team needed.
Final Reflections
I need help with...
Hey, this is Gizmo, your personal cooking companion! Ask me for tips, suggestions, or help on a cooking technique you’re struggling and I’ll recommend you one of our many useful video lessons!
Social
Personal
Receta
9:41
Research Phase
Laying our foundation
Problem Statement
Problem Statement
This is where we define our problem to guide our research. Problem Statement: The current state of cooking/recipe applications has focused primarily on cooking blogs. What existing products/services fail to address is convenience, ability to pull from different sources, and user social interaction. Our product/service will address this gap by providing a fun and unique user interface for cooks to connect, find inspiration, and create their own personalized recipe books.
We defined our problem to guide our research:
The current state of cooking & recipe applications has focused primarily on cooking blogs. What existing products & services fail to address is convenience, ability to pull from different sources, and user social interaction.
Our product & service will address this gap by providing a fun and unique user interface for cooks to connect, find inspiration, and create their own personalized recipe books.
Your recipe organization. Your connectivity.
Your way.
Project Overview
Receta is an all-inclusive recipe import and organization prototype. Our application allows users
to add recipes online or other application with ease. In addition, their is a social forum which is
utilized to allow users to connect with other chefs for culinary advice. The idea was pitch by our
team leader Datsayna Medina at Kennesaw State University.
Receta is an all-inclusive recipe import and organization prototype. Our application allows users to add recipes online or other application with ease.
Additionally, there is a social forum which is utilized to allow users to connect with other chefs for culinary advice.
The idea was pitched by our team leader Datsayna Medina at Kennesaw State University.
Bleak Organization, lack of user cooking assistance, and lack of user freedom
Bleak organization, lack of user cooking assistance, and lack of user freedom
The Problem
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Through our literature review and competitive audit, we discovered that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
The Problem
Hypothesis on user wants and goals
Persona Hypothesis
Through our own fine-tuning we broke town the user goals and behaviors. We concluded that most users should be beginners to cooking and need moderate recipe assistance. However, there is a second option for intermediate users who would require fine-tuning previously made recipes and customizations. With this information, we conclude that beginner users would need basic and simple features, while intermediates should be interested in more in-depth features such as social connection.
Through our own fine-tuning we broke town the user goals and behaviors. We concluded that most users should be beginners to cooking and need moderate recipe assistance. However, there is a second option for intermediate users who would require fine-tuning previously made recipes and customizations. With this information, we conclude that beginner users would need basic and simple features, while intermediates should be interested in more in-depth features such as social connection.
Contacting chefs with various skill level
User Research Interviews
We used our persona hypothesis as a framework for who we would recruit. Since our application can be used by a variety of users we needed to replicate this in our interviews. We selected 5 participants with a variety of cooking skills from pure beginner to experienced expert. We noticed that the beginner's main claims were the need fo cooking help and the experts just need a way to organize and share ideas. However, it really wasn;t until the experienced cooks had a goal of conveniently sharing recipes with others.
We used our persona hypothesis as a framework for who we would recruit. Since our application can be used by a variety of users we needed to replicate this in our interviews. We selected 5 participants with a variety of cooking skills from pure beginner to experienced expert. We noticed that the beginner's main claims were the need fo cooking help and the experts just need a way to organize and share ideas. However, it really wasn;t until the experienced cooks had a goal of conveniently sharing recipes with others.
Contacting chefs with various
skill level
User Research Interviews
Used a variety of chefs with various skill level
Affinity Mapping
Affinity Mapping
Within our interview process, we observed certain traits in our participants. Some we passionate about cooking other were just looking for an easy solution for their cooking routines. However, each person told a unique story. Based on each quality and trait we create affinity maps to map each interviewee's habits, information, challenges, wants, and needs. This data was utilized to form our user personas.
Within our interview process, we observed certain traits in our participants. Some we passionate about cooking other were just looking for an easy solution for their cooking routines. However, each person told a unique story. Based on each quality and trait we create affinity maps to map each interviewee's habits, information, challenges, wants, and needs. This data was utilized to form our user personas.
Contacting chefs with various
skill level
From Low to HI
From Low to HI
Designs
Designs
After our personas and requirements were established, it is time to move into bringing those goals to life. The team collectively utilized the Figjam cloud-based software to visualize and design key paths and validation scenarios for both user types. The validation path is labeled in magenta and the key path in green.
After our personas and requirements were established, it is time to move into bringing those goals to life. The team collectively utilized the Figjam cloud-based software to visualize and design key paths and validation scenarios for both user types. The validation path is labeled in magenta and the key path in green.
Behavioral Variables and Curation
Behavioral Variables and Curation
Persona Creation
Persona Creation
Based on our main observations, we developed behavior variables for each participant to find common patterns. These patterns were utilized to show and identify certain opinions on certain topics and goals. We discovered a strong and identifiable divisions between the beginner cooks vs the experienced cooks. Here we were able to determine that our prototype needed to enhance user freedom and social connectivity. Red represents experienced cooks while green is beginner
Based on our main observations, we developed behavior variables for each participant to find common patterns. These patterns were utilized to show and identify certain opinions on certain topics and goals. We discovered a strong and identifiable divisions between the beginner cooks vs the experienced cooks. Here we were able to determine that our prototype needed to enhance user freedom and social connectivity. Red represents experienced cooks while green is beginner
What did we discover?
Observations
Observations
None of our participants were 100% confident in their cooking abilities
3 out of 5 participants see cooking as a way of self pride
Each person values simplicity and organization
Each person is open to learning new things every day
None of our participants were 100% confident in their cooking abilities
3 out of 5 participants see cooking as a way of self pride
Each person values simplicity and organization
Each person is open to learning new things every day
What did we
discover?
Frameworks/Wireframing Phase
Goals for establishing Goal-Directed Design
Persona Needs and Expectations
Persona Needs & Expectations
Here the team collectivly relized that our problem statement needed to change. We made the executive decision to add more in-depth information in our problem statement. "The current state of cooking/recipe applications has focused primarily on recipe importation and organization. What existing products/services fail to address is the ability to pull from different sources including video formats, education on cooking basics, and user social interaction. Our product/service will address this gap by providing a fun and unique user interface for cooks to create their own personalized recipe books, learn basic cooking essentials, connect, and find inspiration." Our problem statement helped us establish our persona expectations. We covered on requirements relating to communications, skill learnability, organization, and simplicity. Both personas share similar beginning and end goal, however it is the in between in where the requirements differ
Goals for establishing Goal-Directed Design
Here the team collectivly relized that our problem statement needed to change. We made the executive decision to add more in-depth information in our problem statement. "The current state of cooking/recipe applications has focused primarily on recipe importation and organization. What existing products/services fail to address is the ability to pull from different sources including video formats, education on cooking basics, and user social interaction. Our product/service will address this gap by providing a fun and unique user interface for cooks to create their own personalized recipe books, learn basic cooking essentials, connect, and find inspiration." Our problem statement helped us establish our persona expectations. We covered on requirements relating to communications, skill learnability, organization, and simplicity. Both personas share similar beginning and end goal, however it is the in between in where the requirements differ
Energy goes where energy flows
Energy goes where
energy flows
Prototyping
Prototyping
The sample above is not our full wireframe set. The full set is located on our Figjam. We based most of our designs from the wireframe above, however we did not account for the changes and extensiveness with our fine-tuning. We delegated a task of each individual to create 12-15 screens in Hi-Fidelity. However, this caused a little bit of inconsistency. Since we worked on the screens individually our UI was not universal. Later on, we all got together and made the adjustments accordingly. Utlizing a clean and simple aesthetic with a 50s color theme. In addition, we expanded on the used of an 8 pt grid for simple GUI programming, font styles, and text styles
The sample above is not our full wireframe set. The full set is located on our Figjam. We based most of our designs from the wireframe above, however we did not account for the changes and extensiveness with our fine-tuning. We delegated a task of each individual to create 12-15 screens in Hi-Fidelity. However, this caused a little bit of inconsistency. Since we worked on the screens individually our UI was not universal. Later on, we all got together and made the adjustments accordingly. Utlizing a clean and simple aesthetic with a 50s color theme. In addition, we expanded on the used of an 8 pt grid for simple GUI programming, font styles, and text styles.
The people who we are designing for
The people who we are designing for
Personas
Personas
Here are our personas: Bianca Frank, our primary persona that represents the common user in our prototype. Bianca is a small college student that is looking towards utilizing Receta to teach her simple and easy cooking techniques to fit with her diet. Kevin Landry, our secondary persona, he represents a rather more social user that is more familiar within the kitchen. His goal is to utilize receta to learn from other chefs and connect with others in his community.
Here are our personas:
Bianca Frank, our primary persona that represents the common user in our prototype. Bianca is a small college student that is looking towards utilizing Receta to teach her simple and easy cooking techniques to fit with her diet.
Kevin Landry, our secondary persona, he represents a rather more social user that is more familiar within the kitchen. His goal is to utilize receta to learn from other chefs and connect with others in his community.
Refining our flow and interactions based on past users
Usability Testing
Usability Testing
Although we went through our designs many times. The designer is the one who fully knows the inside and outside of a prototype. However, we needed to see if our designs were simple to navigate and matched our users' goals. To gather evidence on how usable our application was, we conducted multiple usability tests with our past interviewees.
Although we went through our designs many times. The designer is the one who fully knows the inside and outside of a prototype. However, we needed to see if our designs were simple to navigate and matched our users' goals. To gather evidence on how usable our application was, we conducted multiple usability tests with our past interviewees.
Refining our flow and interactions
based on past users
Bianca Frank Expectations
Kevin Landry Expectations
View Figma Canvas
View Figma Canvas
What most recipe assistat apps lack
Social Group Chef Threads
During our interviews multiple user asked if they could have a feature to directly connect with other chefs for help. With Receta groups and chats this helps bridge the gap between chefs from all different backgrounds.
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Vegan’s Only
I made pestooooo
@TBGProd58
5m
Brycee
idk what i’m doing lol 🙃
30m
Beginners
Guys idk what I’d do without my air fryer
@Mona_liSa
2hr
Vivienne
Yeah it really helped me learn the ropes
1d
Stells
fr
4d
Start a new chat
My Chats
Groups
Chat
Search
Profile
Social
Personal
Receta
9:41
Receta: Your Recipes, Your Way
Final Prototype
From all our data collected from the market research, competitive audit, usability test, and other important metrics. We present to you Receta: The all-inclusive recipe organization and cooking assistant application. Disclamier: Still a working prototype.
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
View Prototype here
Groups
Chat
Search
Profile
Dinner for Two
Group dedicated to meals for childless couples
Help, I Can’t Cook!
Meals to help you impress any person in your life, no matter your skill level
Similar Groups
Are you looking for meals to share and enjoy with loved one?
Welcome to Friendly Eats, where we help each other make bomb food 🌏
Rules:
Trolling = banned
Be unique
Be yourself
Have fun!
Join Group
360 Members
89 Posts
Friendly Eats
Social
Personal
Receta
9:41
View Prototype here
View Prototype here
View Prototype here
Nothing is ever perfect, however everything requires progress
Final Reflection on the Project
For my first time working with an IAD team I can say it was a great time. We all bonded on a great level and it was simple to generate ideas. In addition, our scheduling was great we did need to spend many hours on our designs, but it was worth it. From research, wireframing, and communicating it was a good flow. Lastly, I want to pay my respects to my team Datsayana Medina, Anna Kahle, and Amanda Wallace for guiding me and providing the help the team needed
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Experiences teaches everyone
Lessons learned
Things I learned for next time:
Time deligations are the most important thing
Universal components for UI is essential for consistency
Time management could have been better
Know the amount of work you are doing before starting the project
Keep user goals always in mind
UX may be important, however my sense on UI and color theory needs to improve
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
Experiences teaches everyone
Lessons learned
Things I learned for next time:
Time deligations are the most important thing
Universal components for UI is essential for consistency
Time management could have been better
Know the amount of work you are doing before starting the project
Keep user goals always in mind
UX may be important, however my sense on UI and color theory needs to improve
Thank you for Navigating Receta :)
Closing Remarks
Receta was a great design foundation for my team and I and I want to show my upmost gratitude for everyone and you for taking the time to see our projectThank you and live a great life. :)
Experiences
teaches everyone
Things I learned for next time:
Time deligations are the most important thing
Universal components for UI is essential for consistency
Time management could have been better
Know the amount of work you are doing before starting the project
Keep user goals always in mind
UX may be important, however my sense on UI and color theory needs to improve
Lessons Learned
Thank you for
Navigating Receta :)
Receta was a great design foundation for my team and I and I want to show my upmost gratitude for everyone and you for taking the time to see our projectThank you and live a great life. :)
Closing Remarks
Thank you for Navigating Receta :)
Closing Remarks
Receta was a great design foundation for my team and I and I want to show my upmost gratitude for everyone and you for taking the time to see our projectThank you and live a great life. :)
My team and I discovered through our literature review and competitive audit that multiple recipe organization applications exist. Common patterns we noticed with these applications were user pay walls, bad user experiences, outdated UIs, and a lack of recipe and cooking assistance for users.
View Prototype here
Easy Meals
Salmon with Brown
Sugar Glaze
Emily Weinberger
Published: 4/23/24
Uploaded from: Simply Recipes
Uploaded to Receta: 5/15/24
Homemade Baked Lasagna
Brandie
Published: 3/27/21
Uploaded from: The Country Cook
Uploaded to Receta: 1/23/24
Sheet Pan Sausage,
Peppers, and Onions
Sheela Prakash
Published: 6/7/24
Uploaded from: Simply Recipes
Uploaded to Receta: 2/2/25
To Die For Fettucine Alfredo
Erin Marie
Published: 2/12/18
Uploaded from: AllRecipes
Uploaded to Receta: 3/12/25
Stuffed Peppers
Rian Handler
Published: 12/9/24
Uploaded from: Delish
Uploaded to Receta: 3/23/25
Chicken Nuggets
Jose.elCook
Published: 3/20/25
Uploaded from: Files
Uploaded to Receta: 4/24/25
Favorites
Lazy Pasta
FitGreenMind
Published: 3/28/24
Uploaded from: YouTube
Uploaded to Receta: 1/23/24
Bibimbap
Kay Chun
Published: 4/13/22
Uploaded from: Bon Appetite
Uploaded to Receta: 7/18/24
Broccoli Beef Ramen
Stir Fry
Nick Evens
Published: 11/4/24
Uploaded from: Simply Recipes
Uploaded to Receta: 3/14/25
Ranch Chicken Crockpot
(Crack Chicken)
Valentina Ablaev
Published: 8/20/22
Uploaded from: Valentina’s Corner
Uploaded to Receta: 4/24/25
Healthy Sides
Jicama Salad
Elise Bauer
Published: 1/10/24
Uploaded from: Simply Recipes
Uploaded to Receta: 4/14/25
Spicy Cucumber Salad
careesekwok
Published: 2/20/25
Uploaded from: TikTok
Uploaded to Receta: 3/16/25
Desserts
Soft and Chewy Sugar
Cookies
Tessa Arias
Published: 9/30/21
Uploaded from: Handle the Heat
Uploaded to Receta: 3/15/25
Grandma’s Cookies
Grandma
Published: Sometime in the 90’s
Uploaded from: Files
Uploaded to Receta: 4/10/25
Bianca’s Cookbook
Cookbook
Prep
Import
List
Help
Social
Personal
Receta
9:41
Ranch Chicken Crockpot (Crack Chicken)
Category:
Select Category
Valentina Ablaev | Valentina’s Corner | Published: September 20, 2022 | Uploaded to Receta: April 24, 2025
Ingredients
Serving Size:
4 servings
2 lb
boneless skinless breast
2
garlic cloves minced
2 Tbsp
ranch powder
3 Tbsp
unsalted butter
1/4 cup
chicken broth
1/2 tsp
salt
1/4 tsp
ground black pepper
8 oz
bacon chopped and cooked
1 1/2 cups
shredded cheese
12 oz
cream cheese room temp
Steps
1.
Add the chicken breast, cream cheese, minced garlic, ranch powder, butter, chicken broth, salt, and black pepper into the crockpot.
2.
Close the lid and cook on high for 3-4 hours or on low for 6-7 hours.
3.
Remove the chicken and using two forks, shred the chicken breast.
4.
Add the shredded chicken, cooked bacon and shredded cheese back into the crockpot and mix. Cook just until the cheese melts.
5.
Serve as desired and enjoy!
Additional Notes:
Save
Cookbook
Prep
Import
List
Help
Social
Personal
Receta
9:41