Tendr

Making recipe discovery faster, playful, and easier to act on.

Background & Mission

A quarter-long team project redesigning a recipe discovery concept to help people decide what to cook based on their ingredients, time, budget, and preferences.

TENDR’s original concept used swiping to help people discover recipes, but lack of features and commitment to the project made it difficult to be seen as a usable application. Our goal was to build up on that concept and make recipes easier to choose through finding and saving recipes in a gamified concept.

Role

UX Research & Designer

Timeline

10 Weeks

Tools

Figma Make

My Contributions

I helped design features such as the cookbook and folder experiences. Working with my team, I contributed to conducting user interviews, competitive analysis, and interactive Figma prototypes.

Impact

We developed and tested a redesigned prototype with four users, using their feedback to refine onboarding, recipe discovery, and saved-recipe organization.

Project Overview

Finding the Gap Between Inspiration
and Action

We interviewed 7 participants and supplemented our findings with webnography and secondary market research to understand how people decide what to cook.

7/7 Checked their fridge or pantry before deciding what to cook.
6/7 Considered time a major factor.
5/7 Were influenced by budget constraints.

Designing Around Decision Fatigue

We found a recurring gap where people were constantly exposed to food inspiration through social media and recipe content, but still struggled to decide what to make and follow through with cooking. With that in mind, we wanted to make swiping the main component in figuring out whether a recipe was interesting enough to save and cook.

Quicker Onboarding

We designed onboarding pages to introduce the core interactions upfront and help users understand how TENDR could support their cooking decisions. We also used the onboarding to understand what users would not want to be suggested to, such as allergens or dietary preferences. Users would not be recommended recipes that didn't meet their needs.

Pantry-Aware Recommendations

We also wanted to recommend recipes that would take into account the pantry and perishable goods that the user has. By doing so, its spontaneous in finding what can be cooked or prepared without worrying about lack of ingredients.

Saving Inspiration for Later

I helped shape the cookbook and recipe folder experience as the bridge between discovery and action. Instead of letting liked recipes disappear into another saved list, users could organize them into folders and return to them when they were ready to cook.

Testing & Iterations

We tested the prototype with users to understand how quickly they could grasp TENDR’s core interactions. Early sessions revealed confusion around onboarding and the swipe experience, which informed revisions to the flow and interface.

55 seconds → <15 seconds
Time to first swipe
50% → 80%
Onboarding success rates
7.5 → <3
Average count of usability errors

What did work

  • Swipe Interaction
  • Ingredient-based discovery
  • Saving recipes

What we would improve upon

  • Clearer Onboarding
  • More accessible colors
  • Concise recipe presentation
  • Recipe sourcing and trust

Due to our quarter-long timeline and limitations with Figma's free plan utilizing Figma Make, we prioritized validating the core experience rather than polishing every interaction.
‍These findings became our roadmap for a future iteration.