Reducing your carbon footprint can be challenging. Our web application can support users reduce their emissions by analyzing their fridge and recommended meals based on carbon-foot print statistics.
Our project was inspired by the Wellness for All track. The carbon emissions level on our planet has reached a dangerous level where scientists say that the result will be irreversible in a few years if we continue on like this. We wanted to focus on how we can improve our own lives while also improving it for those around us by covering physical and environmental health. We believe our project would enhance the well-being of both the individuals and the planet.
FoodPrint is a web application which takes the ingredients the user has inputted and outputs recipes ranked by their carbon level and if the inputted ingredients are in the recipe. It parses through recipes and extracts ingredients from them to match them with what the user desires. When outputting the recipes, it also gives them a carbon level which tells them the total of each ingredient's carbon level in that recipe. This can allow users to make thoughtful decisions and give them a chance to think through the consequences of what they consume.
We built our application through React and Next.js for our frontend features and to integrate our backend. We used Tailwind and CSS for designing some of our pages. We used Suggestic.api to extract recipes from websites that include the users ingredients input and list the carbon level of each recipe so individuals can make informed choices. We used Grok.api to calculate each specific ingredients carbon level and added them all together to have a total for each recipe.
We had a lot of difficulty with connecting our APIs properly. At first, we had researched and decided on using CarbonCloud API but upon clicking on it we found out that you have to wait for a response from a country first before being able to access it. We had a similar problem for our recipe API where the one we wanted to use and extract ingredients from required them to email back with a response. It was difficult finding APIs that would work with our project and afterwards, it was very difficult to connect them and to get them working through inputting the right parameters.
We're proud of the design of our project and the creative way we were able to stick with our project idea even if we had to deviate from our original plan. We problem solved together while also working on tasks individually. We had great teamwork and were able to build on each others work instead of holding each other back.
We learned a lot of skills through coding the web application as well as through the events Cmd-f held on the side. We learned a lot of valuable information through the Opening Ceremony Panelists such as the importance of reaching out to people and taking chances, the recruitment processing values through Bobatalks, and how just taking the chance to Linkediln without fearing rejection can bring opportunities to you through the Networking event.
We think we can enhance FoodPrint by incorporating CarbonCloud instead of Grok to calculate each ingredient's carbon level to improve the reliability of the calculations. We can expand our project through also adding a calorie count to recipes so that users can hit their fitness goals as well as making personal accounts so users can save recipes or queries if they wish.
Log in or sign up for Devpost to join the conversation.