GreenTrace

💡 Inspiration

The issue of global climate change is becoming increasingly severe, and we strongly feel that everyone should contribute to the sustainable development of our planet. However, many people don't know where to start, or feel that individual efforts are insignificant. The inspiration for "GreenTrace" originated from this — we wanted to create a simple and intuitive tool to help the public understand their own carbon emissions and provide practical, actionable reduction tips, integrating environmental actions into daily life. We believe that small actions, when aggregated, can make a huge difference.

🌱 What we learned

In the process of developing "GreenTrace," our team delved deep into carbon footprint calculation methods, carbon emission factors for different lifestyle behaviors, and user incentive mechanisms. We learned:

• The Complexity of Data: Accurately calculating personal carbon footprints involves multifaceted data. Simplifying the calculation model while maintaining its scientific validity was a major challenge.
• User Experience is Paramount: To encourage public adoption, the interface must be friendly, operations must be simple, and recommendations must be practical and easy to implement.
• The Importance of Education: Beyond providing a tool, it's crucial to disseminate environmental knowledge and raise users' environmental awareness.
• The Power of Team Collaboration: Cross-disciplinary knowledge sharing and efficient communication are key to project success.

🛠️ How we built it

1. Requirement Analysis & Design: We first defined the core functionalities — carbon footprint calculation (transportation, diet, energy consumption, etc.), setting carbon reduction goals, environmental knowledge popularization, and user progress tracking. We then proceeded with UI/UX design, striving for simplicity and clarity.
2. Technology Selection: For the frontend, we used React and Tailwind CSS to implement a responsive interface. For the backend, we used Node.js with the Express.js framework, and chose PostgreSQL as the database to store user data and carbon emission factors.
3. Data Collection & Integration: We referenced carbon emission databases from several authoritative institutions and designed a rational data structure.
4. Core Feature Development: We incrementally implemented modules such as user registration/login, carbon emission data input, real-time calculation, and personalized recommendation generation.
5. Testing & Iteration: We conducted multiple rounds of internal testing and continuously optimized features and user experience based on feedback.

💪 Challenges we ran into

• Data Accuracy and Localization: Carbon emission factors vary by region, making it a significant challenge to provide more precise localized calculations. We initially used generic data and plan to incorporate more regional data in the future.
• User Retention: How to keep users engaged with the app and practicing carbon reduction actions after their initial understanding of their carbon footprint is an ongoing consideration. We are trying to incorporate gamification elements and community sharing features to increase stickiness.
• Cross-Platform Compatibility: Ensuring a consistent and good experience across different devices and browsers required meticulous debugging.
• Time Constraints: Completing all envisioned features within the limited time of a hackathon placed high demands on the team's time management and execution capabilities.

Built With

• css3
• express.js
• express.js-database:-postgresql-apis:-(e.g.
• figma
• git
• github
• heroku-(for-application-deployment)
• html5
• if-none
• javascript
• javascript-(es6+)
• leave-blank)-design-tools:-figma-collaboration-tools:-git
• netlify-(for-frontend-deployment)
• node.js
• open-carbon-api-(if-used-for-carbon-emission-data)
• postgresql
• react
• slack
• state-"n/a"-or-leave-blank)-cloud-services:-(e.g.
• tailwind
• tailwind-css-backend:-node.js