Receta: Cooking assistance and social connection application
Role
UX/UI Designer/Researcher
Approach
Culinary
Duration
2 months
Medium
Food and Hospitality
Receta: Cooking assistance and social connection application
Role
UX/UI Designer/Researcher
Approach
Culinary
Duration
2 months
Medium
Food and Hospitality
Receta: Cooking assistance and social connection application
Role
UX/UI Designer/Researcher
Approach
Culinary
Duration
2 months
Medium
Food and Hospitality
Project Overview
Your Recipe orgnization, Your connectivity, and Your way
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.
Project Overview
Your Recipe orgnization, Your connectivity, and Your way
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.
The Problem
Bleak Organization, lack of user cooking assistance, and lack of user freedom
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.
Problem Statement
Laying our foundation
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.
Persona Hypothesis
Hypothesis on user wants and goals
Most users will be beginner cooks who need simple, guided recipe support. A smaller group of intermediate users will want more advanced features, like customizing past recipes and engaging in social or community-driven interactions. Beginners benefit from basic tools, while intermediates look for deeper, more connected experiences.
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?
User Research Interviews
Used a variety of chefs with various skill level
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.
Affinity Mapping
Tracking our data and sorting it
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.
Observations
What did we discovered?
1. None of our participants were 100% confident in their cooking abilities 2. 3 out of 5 participants see cooking as a way of self pride 3. Each person values simplicity and organization 4. Each person is open to learning new things every day
The Problem
Bleak Organization, lack of user cooking assistance, and lack of user freedom
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.
Problem Statement
Laying our foundation
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.
Persona Hypothesis
Hypothesis on user wants and goals
Most users will be beginner cooks who need simple, guided recipe support. A smaller group of intermediate users will want more advanced features, like customizing past recipes and engaging in social or community-driven interactions. Beginners benefit from basic tools, while intermediates look for deeper, more connected experiences.
User Research Interviews
Used a variety of chefs with various skill level
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.
Affinity Mapping
Tracking our data and sorting it
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.
Modeling and Requirements
Persona Creation
Behavioral Variables and Curation
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
Persona Creation
Behavioral Variables and Curation
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
Modeling and Requirements
Personas
Laying our foundation
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.
Persona Needs and Expectations
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
Research Phase
Bianca Frank Expectations
Kevin Landry Expectations
Project Overview
Your Recipe orgnization, Your connectivity, and Your way
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
Observations
What did we discovered?
1. None of our participants were 100% confident in their cooking abilities 2. 3 out of 5 participants see cooking as a way of self pride 3. Each person values simplicity and organization 4. Each person is open to learning new things every day
The Problem
Bleak Organization, and lack of user freedom
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.
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?
Problem Statement
Laying our foundation
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.
Persona Hypothesis
Hypothesis on user wants and goals
Most users will be beginner cooks who need simple, guided recipe support. A smaller group of intermediate users will want more advanced features, like customizing past recipes and engaging in social or community-driven interactions. Beginners benefit from basic tools, while intermediates look for deeper, more connected experiences.
Personas
Laying our foundation
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.
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?
User Research Interviews
Used a variety of chefs with various skill level
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.
Affinity Mapping
Tracking our data and sorting it
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.
Frameworks/Wireframing Phase
Designs
From Low to HI
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.
Observations
What did we discovered?
1. None of our participants were 100% confident in their cooking abilities 2. 3 out of 5 participants see cooking as a way of self pride 3. Each person values simplicity and organization 4. Each person is open to learning new things every day
Bianca Frank Expectations
Kevin Landry Expectations
Modeling and Requirements
Persona Creation
Behavioral Variables and Curation
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
Personas
Laying our foundation
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.
Persona Needs and Expectations
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
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
Bianca Frank Expectations
Kevin Landry Expectations
Prototyping
Energy goes where energy flows
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
Frameworks/Wireframing Phase
Designs
From Low to HI
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.
Frameworks/Wireframing Phase
Social Group Chef Threads
What most recipe assistat 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.
View Canvas
Prototyping
Energy goes where energy flows
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
Designs
From Low to HI
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.
Prototyping
Energy goes where energy flows
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
Usability Testing
Refining our flow and interactions based on past users
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.
Final Iterations and flows
It all comes down to this
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.
Cook Book Flow
The Main Key path
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
Social Group Chef Threads
What most recipe assistat 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.
Copyright 2025 by Trent Gwyn
AI chat bot feature
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.
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.
Final Reflection on the Project
Nothing is ever perfect, however everything requires progress
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
Lessons learned
Experiences teaches everyone
Things I learned for next time: 1. Time deligations are the most important thing 2. Universal components for UI is essential for consistency 3. Time management could have been better 4. Know the amount of work you are doing before starting the project 5. Keep user goals always in mind 6. UX may be important, however my sense on UI and color theory needs to improve
Closing Remarks
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 project Thank you and live a great life. :)
Usability Testing
Refining our flow and interactions based on past users
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.
Usability Testing
Refining our flow and interactions based on past users
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.
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 chat bot feature
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.
Final Iterations and flows
It all comes down to this
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.
Final Iterations and flows
It all comes down to this
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.
Final Reflection on the Project
Nothing is ever perfect, however everything requires progress
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
Lessons learned
Experiences teaches everyone
Things I learned for next time: 1. Time deligations are the most important thing 2. Universal components for UI is essential for consistency 3. Time management could have been better 4. Know the amount of work you are doing before starting the project 5. Keep user goals always in mind 6. UX may be important, however my sense on UI and color theory needs to improve
Closing Remarks
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 project
Cook Book Flow
The Main Key path
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
Cook Book Flow
The Main Key path
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
Social Group Chef Threads
What most recipe assistat 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.
Ai chat bot feature
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.
Research Phase
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.
Final Reflection on the Project
Nothing is ever perfect, however everything requires progress
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
Lessons learned
Experiences teaches everyone
Things I learned for next time: 1. Time deligations are the most important thing 2. Universal components for UI is essential for consistency 3. Time management could have been better 4. Know the amount of work you are doing before starting the project 5. Keep user goals always in mind 6. UX may be important, however my sense on UI and color theory needs to improve
Closing Remarks
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 project Thank you and live a great life. :)