SAVR Recipes App

Tasty recipes made simple with guided steps

Overview

This project is a version of a Google Venture design sprint with Springboard and BiteSize UX. In a five day timeframe I sprinted a solution for a recipe app which offers step by step instructions for users to cook delicious meals at home.

Parameters

Timeline:

• April 15 - 20, 2025

Day 1: Mapping

My Role

• Solo UI/UX Designer

• Solo UX Researcher

• Solo Product Designer

The Problem

• People want to cook at home but sometimes struggle to follow complex instructions

• People can be frustrated with the outcome of their cooking

• Instruction timelines can be unrealistic

2.User wants to find and cook easy recipes

User scrolls for recipe > Settles on recipe > Follows recipe steps > Prepares meal > User eats meal

Deliverables

Solution

A platform that:

• Provides a variety of recipes with time-based, step-by-step instructions that clearly break down each stage of the preparation process

In order to gain a better understanding of the problem, I analyzed the research, interviews, and persona which were provided by BiteSize UX.

These are the pain-points and goals that I found:

Pain Points

• Unfamiliar ingredients make trying new recipes difficult and intimidating.

• Lack of clear, time-based instructions leads to confusion during cooking.

• Steps not synchronized ( multitasking guidance like "prep this while that cooks") increases stress.

• Recipes that are not accurate in timing create frustration and impact the cooking outcome.

• Overly complex or unclear steps can lead to poor results and lower confidence.

Goals

• Individuals want to follow clear and straight forward instructions that accurately reflect the amount of time that it will take to make a meal.

• People want to browse meals and filter based on what they want to eat.

End-to-end experience mapped

Below are three potential solutions:

1. User wants to find and cook new recipes

User explores possible recipes > Finds recipe > Follows recipe > Makes meal > User cooks and eats meal

User looks for recipes > Selects recipe > Follows easy instructions > Preparation times match expectations > User eats meal

3. User wants to cook and eat tasty recipes

Final Map

After analyzing the three possible solutions, I decided that map two is the best design in order to help users reach their desired outcome. Below is the final version:

Day 2: Sketching

In order to gain inspiration from similar products providing solutions to users, I utilized a lightning demo to better understand; Tasty Recipes, NYT Cooking, and Mealime Meal Plans & Recipes. Below are some of the features I liked:

1. Step-by-step instructions with guided videos

2. AI assistant to help find tailored recipes

3. Shopping recipe integration

4. Hands free cooking instructions

5. Nutrition information for every recipe

Sketching possible screens with crazy 8s

Using the information learned during the lightning demos, I sketched out possible solution screens. Five of the eight sketches represent the recipe page.

Final Critical Screen

I decided to go with this screen for these reasons:

• Provides the most straightforward approach to following instructions

• Each recipe step has its own card to ensure the user does not become overwhelmed

• Each card contains time estimates and is organized in order

Solution Sketches

After designing my critical screen, I sketched a three panel solution which demonstrates how the critical screen will function.

Day 3: Deciding

Below is a storyboard which I created focusing on the key elements identified in the previous sprint days:

Detailed instructions, time estimates, and cookware recommendations

Day 4: Prototyping

Day four was spent creating high-fidelity prototypes which include the critical screen and several screens from the storyboard.

Day 5: Testing

I conducted a single round of usability testing with five users. Below is what I learned:

Issues Encountered and Possible Solutions

Time constraints prevented me from iterating on the design. Below are some issues and possible solutions:

1. “Save recipe” functionality is confusing

Users expected a clear save button on individual recipe pages.

Proposed Solution: Save button on each recipe page.

• Sketching

• Mapping

• Storyboarding

• Crazy 8’s

• High Fidelity Wireframes

• Usability Testing

• Lightning Demos

Key Takeaways

1. Utilizing a design sprint is an efficient and effective way to create and test ideas

During the design sprint process I gained valuable skills in time management, prioritization, and operating under tight deadlines.

2. Staying focused on the big picture

Staying focused on the end goal was crucial during this design sprint, it can be easy to become held up on small details and lose sight of the end goal.