What is your chosen theme and problem statement?

Our chosen theme is Environment, and our problem statement is as follows: “In 2019, Singapore generated around 744 million kg of food waste. How can we tackle this growing problem and encourage Singaporeans to cut down on unnecessary food waste?

What does your hack do?

Goodshare & Co. is a social food sharing platform that enables the average home-owner to easily share and redistribute excess food resources to neighbors, or donate to the needy.

Users will by default be sorted into a group chat with other individuals within a certain radius. They can then either request for items they are lacking in their household, or list foods to share with others in their vicinity.

For example: a “Sharer” can take a picture of a carton of milk that is expiring soon and would normally be thrown away, then make a post on our platform notifying neighbors within his HDB block that the carton of milk is up for grabs. The neighbor can then make his way to the appropriate unit and collect the carton of milk. The “Sharer” will earn points that can be redeemed at partnered establishments.

How does your hack answer the problem statement?

From research and personal experience, we found that one of the most common reasons for food wastage was consumers buying more food and ingredients than required, perhaps due to unforeseen circumstances or impulse purchasing. While there are many enterprise solutions that seek to eliminate wastage in the supply chain, few are focused on the redistribution of excess food specifically at the grassroots community level.

Our hack tackles this wastage of expiring goods or uneaten foods by providing users with a convenient and easy way of recycling. By fostering a sense of community, making the recycling process convenient, and incentivizing recycling, Singaporeans will be more motivated and willing to do their part in reducing unnecessary food waste.

How did you build your hack?

We sought to create a web application with suitable room for expansion into mobile app development, using a robust API written in Python and a performant yet accessible web front-end written in Javascript using the Svelte framework.

What are some difficulties you overcame?

One of our greater difficulties over the course of the 24 hours was time. Ultimately, in such a web application, having to split the front-end and back-end meant that one side would have to wait for another for the implementation to work, especially with limited time for mock testing. Additionally, we were unable to implement some of the features that we wanted due to time constraints. Regardless, with proper communication of each sides’ requirements and difficulties, we were able to complete the application in the allotted time. Another difficulty we encountered was in the ideation phase. Attempting to conceptualize a hack that is relevant to the problem statement, creative, and useful to society all at once was a challenge to say the least. As a developed country, many of the ideas that we came up with had already been done before, or were simply unrealistic to implement as it required resources far in excess of what we had on hand. Thus, we spoke to neighbors and conducted research online to become more familiar with the food wastage situation in Singapore. By gaining familiarity on the subject matter, we were able to identify areas of weakness, and by extension, opportunities to create a hack within the food wastage space.

What was your biggest learning point from LifeHack 2022?

Our biggest learning point was how important communication is in ensuring all members of the team are on the same page. Initially, everyone was working on their individual parts and communicating only when needed. This resulted in a disjointed and messy working environment. Once we consolidated our progress on individual parts of the project in a simple Google sheet however, progress became far more smooth sailing as we were all cognizant of what other team members were doing, as well as what they needed from other members of the team. We would then individually know what tasks to prioritize in order to not hold back other members of the team.

Built With

Share this project: