Up-Kick is an app that is designed and catered to at-home chefs who want healthy and budget-friendly solutions to improve the flavors of home-cooked meals. It provides recommendations based on the users' flavor profiles, allergies, and dietary restrictions. They are also able to connect with other users to view their recipes, and view videos from professional chefs.
With the massive rise in food delivery and meal kit options, people are becoming more distant from what they eat. The rising costs of restaurants and delivery services are unsustainable for regular consumption, and the lack of awareness of ingredients used raises health concerns.
Up-Kick offers recipe-building for spices and sauces to be used as an addition to enhance any homemade meal. Recommendations are offered based on the users' custom-set flavor profiles, food allergies, and aversions. Your recipes can be shared with friends, and you are able to view their custom blends as well.
I looked at 3 different companies and followed up with a comparison using Nielsen's heuristics:
My screener survey had 23 responders across various demographics - these were the largest takeaways from the data that was collected:
Of the 23 responses to the screener survey, I selected 5 participants to interview for information. Though many had common grounds, the most significant standouts cooked at home due to dietary constraints, or to provide healthy options to their children.
These responses had a great impact on how I would approach personas, user stories, and empathy maps - all of which presented a clear pathway to honing in on MVPs.
Based on my continued synthesis from the screener and interviews, I found that diet and family were the biggest individualistic contributors. This led to the creation of 2 personas: Vegetarian and Parent.
I wanted to better understand how each component would communicate with the others. Laying everything out clarified how to accomplish the primary tasks: make a new recipe, add ingredients, save to a category, and view it at any time.
Creating an early iteration was an invaluable resource because I was able to see layouts compared to other apps, and pay attention to the UI standards when visualizing redesigns.
I rebuilt my sketches into low-fidelity wireframes using Figma. With the sketches being a solid baseline, I wanted to make changes to the initial screens with ones that adhere more closely to UI standards. The features that remained from initial sketches became more refined.
Taking wireframes through the next phase required preparation; I needed consistent colors, icons and fonts throughout each screen.
Now that I had my red routes solidified, it was time to begin designing the high-fidelity screens. I wanted a dark theme with a strong contrast for the primary and secondary colors.
Using Figma, I built a high-fidelity prototype with my first screen iterations. I recruited and interviewed 5 participants for round 1, then 5 new participants for round 2 after correcting the initial issues. These were the top 3 problems that the tests highlighted:
Issue 1: The formatting for the Categories and Recipes pages caused confusion.
Solution: Reformat these screens with visual components and clear buttons.
Issue 2: Discover page confused users and didn't add anything worthy of having its own page.
Solution: Eliminate this page and add a search feature in the top navigation bar.
Issue 3: No way to connect and view other users and their recipes.
Solution: Create a community page.
After addressing the necessary changes I learned from user testing, I created my final design using Figma.
The above images are the final screens for the project within the timeline of the academic project; however, after gaining more experience as a designer, I came back and rebuilt some of those screens to have a more refined look and feel - these images are posted below: