-
Recipe Book view of all unmodified staples
-
Let's subsribers choose which meal of the week they have leftovers for
-
Let's the user pick which leftovers, seperating between raw ingredients and cooked leftovers
-
One of the recipe options for a given leftover. The light green box shows the step used to modify the staple with our leftover
Inspiration
We wanted make something that improves a well defined scenario, without necessarily throwing ML at it at all cost. We wanted to provide both increased options for meal customization, reduce food waste and provide analytics about customer habits.
What it does
Our App, Between the Box, lets a HelloFresh subscriber connect their account and displays the recipes that they got in their latest deliveries. In case they have cooked leftovers or don't want to use all the raw products from a recipe, they can easily get suggestions on quick and tasty staples that can be modified with their leftovers.
Alternatively users can also look at the recipe collection without modifications.
The data collected can be used to analyze customer behavior and which produce gets used or which recipes commonly produce leftovers.
How we built it
Built entirely in Swift. Design Prototypes done in Figma.
Challenges we ran into
Since our team only consists of 2 people, we had to be selective about our scope and how much we would be realistically able to accomplish.
Accomplishments that we're proud of
Figuring out a realistic workload that we can accomplish together. Also challenged ourselves to learn Figma and get better at design.
What's next for Between the Box
The backend can be extended to use real data instead of our mock backend. Additionally, the choice of provided recipes and modifications could also be extended with ML.
The backend can then also be extended to analyze consumption habits and information about recipes, like how often they produce leftovers or which staple modifications are popular.
Log in or sign up for Devpost to join the conversation.