What2Eat - Error 418

Inspiration

We've all had the common dilemma of having a random assortment of foodstuff in our fridges and pantries. Our next question was, what could we make with what we had left over?

What it does

What2Eat is an application that asks the end user to key in the ingredients they have available, and returns recipes using the closest match of ingredients.

How we built it

We used Python for the backend combined with Flask, receiving API Data using the Edamam Recipe Search API.

Challenges we ran into

Determining how we were going to process data exchange between the frontend and backend was difficult; initially we were looking to use Firebase but upon further deliberation it was more feasible to use Flask instead.

Accomplishments that we're proud of

The recipes produced at the selection page will display the number of ingredients and the caloric value of the food from the API in case the user wishes to determine a health conscious choice.

What we learned

We are early on in the scene of hackathons, and we have learned API connectivity, queries, backend to frontend data processing. We have a long way ahead but we are confident.

What's next for what2eat - Error 418

Reduce data usage to/and provide more results for the user to choose from, object recognition from an image in order to automatically consider available ingredients within constraints, display breakdown of nutritional value where available