Foodr App

A mobile app to help users find recipes to cook easily.
Role: Developer
food app on an iphone in foreground

Background

As broke college students, we had trouble finding healthy, cheap food options. Food delivery services had high hidden costs and fast food was too unhealthy to eat every day. With school and projects and work, taking the time to figure out what to cook was difficult. Our generations short attention span fostered a love for apps like 'Tinder', where you make fast paced decisions. This is why we modelled our app with the swiping idea in mind.

What is the Problem?

Uber Eats high costs: Users are frustrated with they get hit with delivery and extra fees when they just want food.
Time constraints: Searching for recipes is time consuming, and college students do not have much time to spare.

What is the minimum viable product? (MVP)

The key goals of the app were to create an iOS app, useable on the iPhone, with a basic interface including a swiping page, individual recipe pages, a cookbook of saved recipes and a recipe planner.
We did market research and found a competing app, 'Tender', that ended up being taken off the app store because of too much traffic.
After identifying the problems, we created a Figma file to design our basic user interface.
We implemented functionalities by starting with the home page and expanding to the individual recipe pages.

What is the product roadmap?

Week 1: Interface Design
Weeks 2-3:
Basic Features Implementation (swiping, saving to cookbook, viewing cookbook)
Weeks 4-5: Database Creation, Advanced Features Implementation (viewing a single recipe, add filters, meal planning) and Testing
Weeks 6:
Refinement based off user feedback

What is the user journey?

Brayden, a college student is home around dinnertime and is getting hungry. The problem is, he is not sure what to make. He doesn’t want to order takeout again since his credit card bill has already been racking up with Uber Eats charges. Brayden pulls out his phone and opens the Foodr application. He selects the vegetarian options and begins swiping. He then finds a recipe for Alfredo pasta that he likes and swipes right. He goes to the “Cookbook” tab and follows the recipe.

How do we measure success?

Although the app has not yet reached a product launch or user testing, I identified some key performance indicators (KPI's) to measure success in the future.
Sign up a minimum of 50 users.
50% of users save more then 5 recipes.
20% of users utilize the meal planning feature,

Final product

a phone showing main page of an app with a chicken alfredo recipe and a heart and x buttons
a phone app showing saved recipes
a phone app showing selecting recipes and the date at the top
a phone app showing planned recipe and the dates