By
@TejalK
This tracker allows one to estimate, visualize and caution carbon dioxide emissions resulting from daily digital activities.
@TejalK
on
Digital Carbon Footprint Calculator
I built a Digital Carbon Footprint Calculator — a web app where you input your daily digital habits (emails sent, HD/4K streaming hours, cloud storage, calls, web browsing, crypto transactions) and it estimates your CO₂ footprint in real time, breaking it down by activity with charts and translating the number into a relatable equivalent (trees needed per year to offset it). The trickiest part was redesigning the UI to make dense data feel approachable — going from a flat, static layout to a dashboard with collapsible sections (emission factors, charts, tree impact) so it explains the "why" behind the number instead of just spitting it out. I'm proudest of the emissions-factor transparency table, since it turns the tool from a black-box calculator into something that actually teaches people where their digital carbon cost comes from. To test it, just open index.html, plug in some usage numbers on the left panel, hit "Generate Insights," and explore the breakdown pie chart, comparison bar chart, and tree-impact card on the right.
@TejalK
on
Digital Carbon Footprint Calculator
1h 31m 23s logged
Revamped the Digital Carbon Footprint Calculator from a flat, static two-panel layout into a dark dashboard-style UI: swapped light-blue panels for a navy/cyan theme, replaced plain number inputs with sliders for continuous values, and broke the results into collapsible sections (View Emission Factors, View Charts, See Tree Impact) instead of dumping everything at once. Added a transparent emissions-factor table so users can see exactly how their footprint is calculated, plus a “Tree Impact” card that translates the raw CO₂ figure into a relatable equivalent (trees needed per year to offset it) - turning the tool from a bare calculator into a clearer piece of climate communication.
@TejalK
on
Digital Carbon Footprint Calculator
I made EcoDigital Tracker, a web app that estimates the carbon footprint of everyday digital habits like emails, streaming, cloud storage, calls, and browsing, giving a CO₂ estimate, a Normal/High/Severe rating, and a chart breakdown. The hardest part wasn't the coding but the deployment - I rebuilt it from a Tkinter desktop app into a Streamlit web app, then worked through a string of deployment errors like a missing requirements file and the wrong version accidentally going live. I'm proud that I kept the layout, fields, and output exactly the same through the rebuild, so it still feels like the original app, just accessible from a browser now. To test it, just open the link and enter any numbers for the usage fields, then hit "Generate Insights" and "View Charts" - no setup needed.
@TejalK
on
Digital Carbon Footprint Calculator
47m 11s logged
I’d already built the core of EcoDigital Tracker before deciding to bring it into Stardance, so this session was about picking it back up and turning it into something actually shareable. It started as a desktop app built with Tkinter — you could enter your daily digital habits (emails, streaming, cloud storage, calls, browsing) and get back an estimated carbon footprint in grams of CO₂, along with a Normal/High/Severe status and a pie + bar chart breakdown. The problem was that it only ran on my machine — no link, no way for anyone else to try it without installing Python themselves.
So I rebuilt the UI in Streamlit, keeping the exact same layout, input fields, output format, and charts, just swapping the framework underneath so it could run in a browser instead of a native window. I also wrote a short README explaining what the tool does and why I built it: to show people how much carbon their everyday digital activity actually produces, and where it lands on the Normal/High/Severe scale.
From there I moved on to getting a real public link. I tried ngrok first to tunnel my local server, but the download got flagged by my antivirus, so I switched to deploying properly instead. I pushed the project to GitHub and connected it to Streamlit Community Cloud, then worked through a chain of deployment errors — a missing requirements.txt that meant matplotlib wasn’t installed on the server, a main file path pointing at a filename with no .py extension, and the old Tkinter file accidentally being the one that got deployed instead of the Streamlit version. Fixed each one by correcting the filenames and adding requirements.txt directly on GitHub.
