Midterm project – Foodprint


Foodprint is a recipe finding app that creates a meal itinerary with zero-waste. The algorithm is still a work in progress, but the design has now been put in place with this midterm.

It’s a simple three page layout. The first page is the ‘Planner’ page where you schedule how many meals you’d like to make that week/timeframe. As you select recipes, they will link from that page. The yet-to-be-determined part will be if you want to make ___ recipes a week, what percentage of those do you select, and what percentage are selected for you based on your interests.

The second page is the ‘Recipe’ page where you can search from the recipes. I am currently pulling from the Campbell’s Soup API, but it’s fairly limited, and like all recipe API’s, it will involve money when you start looking at many different recipes. What I need to do is have a server with a massive JSON file on it, and reference that. Especially for figuring out what recipes will fill out the remaining cooking list, it’s going to have to reference the ingredients of each recipe quickly and effectively, which can’t really be a bunch of calls to a paid API. When you select a recipe, it will also ask you how many servings you’d like to make.

The third page is the generated ‘shopping list’. As recipes are selected, the ingredients needed to purchase appear here. This will be the hopeful key, as it will never say ’3/4 of an onion’ or ’1/2 chicken breast’. It will always be easily purchasable, whole items, that will be completely used up.

The app took a lot of time for me, someone who has never programmed an app before. I would spend hours just trying to figure out how to properly center a jquery menu. I think I have a much better idea of where to look and what to do now, but it did take some time just to get this layout down.

As I mentioned in my presentation, this, for me, is the first step of a paradigmatic shift in how we grocery shop. This app inspired me to think about how we currently purchase groceries and waste so much food. The bigger issue for me is actually the packaging. Food waste is a huge issue, but arguably a worse one is the amount of packaging we use for that food. I have to decide what I want to focus on and why for my final project, and I’m not sure just trying to formulate the algorithm for less waste is worthwhile enough – as though that makes someone’s life easier, it’s really just a small convenience over figuring it out themselves how to use up all the food…and when it comes down to it, so much of the onus is still on consumers to actually follow through and minimize or eliminate waste. However, if this app could be a useful tool to lead to a much bigger idea, I do see value in it. Not that I don’t the other way, but I just want to make sure I’m working towards something worthwhile enough that it’s not just that standard app that’s ‘like this but has this one difference’.

Here are a couple of screenshots.

Screen Shot 2015-03-26 at 1.00.15 AM Screen Shot 2015-03-26 at 1.00.29 AM

Screen Shot 2015-03-26 at 1.00.29 AM

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>