Greeney | Devpost

GIF
Welcome to Greeney
Dashboard page
About page

💫Inspiration💫

We as a group wanted to have a project that was green related and would help people lower their emissions. We decided to make a modern carbon emissions tracker that automatically gathers data from resources such as flights, Uber rides, and food delivery sources to let users track their emissions from multiple sources and empower users to take action by seeing where their carbon emissions are coming from.

🚀What it does🚀

Greeney allows users to gather their emission sources into one app by scraping through a user's receipts to automatically calculate the emissions from sources such as Uber, Doordash, and Lyft. Along with our automatically scraped resources we allow users to fill in a research-backed questionnaire to allow users to see even more data on their emissions.

🛠️How we built it🛠️

Greeney is built using two main technologies, Next.js as our frontend framework and Flask for our backend framework. Greeney uses the oauth 2.0 protocol to connect to a user's email account to view emails and then utilizes the Google gmail api to scrape through receipts to gather user's mobile orders and rides such as Uber and Lyft. We then pass this data into our main carbon emissions calculation which utilizes the Google maps api to calculate distances in order to do calculations required for calculating emissions. Afterwards the data is showcased in beautiful charts using shadcn allowing the user to view their emissions data.

🚧Challenges we ran into🚧

Initially we had no clue how to go about this project, we were unsure if we were even going to able to gather valuable date from user's receipts and were discouraged by the fact that api's such as Uber and Doordash are locked behind developer accounts. However thanks to Google's gmail api we were able to get a foothold to start the project from and from there were able to continue our development with good data for calculating emissions.

🎉Accomplishments that we're proud of🎉

Everybody in this project played a huge role, thanks to the nature of this project we were able to split development into three main sections of data gathering, data processing, and data showcasing. Getting all these components working individually then combining them was a huge feat and we are glad that we were able to get it done.

🎓What we learned🎓

We believe this project was really good example of what a development cycle looks like in the real life and we felt this project improved us all as developers. There were multiple times were we had to communicate with each person's role to make sure we each got what we needed and of course solving many merge conflicts.

🏗️What's next for Greeney🏗️

Currently Greeney's gmail api is in the developer phase only allowing user's who have been added into the development test utilize all of Greeney's capabilities. A potential next step for for Greeney could be going through Google's verification in order to ship Greeney to multiple users.