Curbing food waste for a sustainable future TreeHacks 2019
The awareness vertical - Every year food companies throw away an excess amount of food. According to the Food and Agriculture Organization of the United Nations, “roughly one-third of the food produced in the world for human consumption every year — approximately 1.3 billion tonnes — gets lost or wasted.”
With this in mind, we brainstormed a way for food companies and restaurants to make use of the extra amount of food produced. With the two day time constraints and team skills, we decided to make a web application for a normal consumer to buy excess food based on the desired location radius. The business would signup and login to post food. The consumer would be able to buy discounted food from the post. How we built it For our project, we built our web pages using HTML, CSS, and JavaScript. Our choice of database was Firebase, and we used it with flask as our framework. Our backend was created using Flask and Python.
A challenge was using Flask with Firebase. The documentation was skewed to a pure Python solution with python-admin. Time should have been used to pyrebase, a python wrapper for the Firebase API. Another challenge was developing for the real-time database section for Firebase. We opted for Firestore instead. Accomplishments that we're proud of We are proud of the idea and the application made. We did code it completely on scratch and used productively utilize agile methodologies. The idea is very unique and we hope to be able to spread awareness of saving food waste with this application.
Everyone learned different things throughout this project. However, after discussing and solving our problems, we have all gained a better understanding of the full stack environment. We have also all learned how to use firebase for web applications alongside Flask.
The next steps for FoodCloud would be having better design or identity. Projects should have consistency with the design as noted by the Scott Forstall, creator of IOS. Another must-have feature is having a better schema with the user/business Firebase database.