DEV Weekend Challenge Winners: Earth Day Edition Announced
The dust has settled, the pull requests are merged, and the winners of the DEV Weekend Challenge: Earth Day Edition have been announced. đ⨠Congratulations to all participantsâespecially the winnersâfor turning code into climate-conscious creativity.
But as someone who reviewed dozens of submissionsâfrom carbon footprint calculators to tree-planting gamification appsâI noticed a pattern. Beneath the surface of good intentions, many entries stumbled on the same pitfalls. Letâs talk about them.
Because building a meaningful Earth Day project isnât just about green themes and SVG leaves. Itâs about technical integrity, user empathy, and real-world impact.
Hereâs what most people got wrongâand what the winning entries did differently.
đŤ Common Mistakes (And Why They Matter)
1. Hardcoded Data = Broken Sustainability
So many apps used hardcoded COâ values like:
const carEmissions = 0.404; // kg CO2 per km
But where did that number come from? A 2015 sedan in Germany? An EV in California? A diesel truck in India?
Gotcha: Emissions factors vary wildly by region, vehicle type, and energy mix. Hardcoding makes your app inaccurateâand worse, misleading.
Pro insight: Use real data sources. The IEA, EPA, or open APIs like Carbon Interface provide dynamic, location-aware emissions data. Winners used these. Losers guessed.
2. No Input Validation (Especially for User Numbers)
I saw apps crash when users typed â5kâ instead of â5000â into a mileage field. Or worseâsilently accepted â-100 kmâ as a valid commute distance.
Gotcha: Unvalidated input leads to absurd outputs. A negative commute implies carbon credits for staying home? Thatâs not a feature. Itâs a bug.
Pro insight: Always validate and sanitize. Use libraries like yup or zod, or at minimum:
const distance = Math.max(0, parseFloat(userInput));
if (isNaN(distance)) {
showError("Please enter a valid number");
}
Winning entries handled edge cases like NaN, infinity, and negative values gracefully.
3. Overcomplicating the UI
Some submissions looked like NASA control panels: 15 sliders, dropdowns for every variable, and a modal asking for your blood type âto calculate metabolic emissions.â
Gotcha: More options â more useful. Cognitive overload kills engagement.
Pro insight: The best apps followed the 80/20 rule. They asked for just enough input to give meaningful feedback. One winner calculated footprint from just three inputs: diet type, home energy source, and weekly commute distance.
Simplicity with accuracy wins every time.
4. Ignoring Accessibility
Color-coded impact meters using only green-to-red gradients? No ARIA labels on interactive charts? Text contrast at 1.2:1?
Gotcha: If your climate app isnât accessible, itâs not inclusive. And inclusivity is part of sustainability.
Pro insight: Winners used semantic HTML, proper contrast ratios, and descriptive labels. One even added a screen-reader-friendly summary of emissions impact. Thatâs not just niceâitâs responsible engineering.
đĄ Non-Obvious Wins (What the Top Entries Did Differently)
1. They Made Data Actionable
The best apps didnât just say: âYou emit 2.3 tons/month.â They said:
âThatâs like driving from NYC to LA 3 times. To offset it, you could:
- Switch to a bike 2x/week (saves 0.4t)
- Eat plant-based 3 days/week (saves 0.6t)
- Install solar panels (saves 1.8t/year)â
Insight: People donât change behavior based on numbers. They change based on relatable comparisons and clear next steps.
2. They Used Localized Defaults
Instead of making users guess their gridâs carbon intensity, top apps:
- Detected location via IP (with permission)
- Pre-filled regional averages
- Let users override if needed
One app even pulled local public transit schedules to suggest greener commutes.
Insight: Reduce friction. Assume smart defaults. Let experts tweak.
3. They Avoided âCarbon Shamingâ
The tone matters. Apps that said âYouâre killing the planet!â had poor UX.
Winners used positive reinforcement:
âGreat job! Youâre in the top 30% of low-emission commuters. Keep it up!â
Or:
âSwitching to renewable energy could cut your home emissions by 70%. Want to explore providers near you?â
Insight: Sustainability is a journey. Meet users where they are.
4. They Thought Beyond the App
One winning entry didnât just calculate footprintâit generated a PDF report with:
- Personalized reduction tips
- Links to local recycling centers
- A QR code to plant a tree via a partner NGO
Another integrated with Strava to auto-track bike commutes.
Insight: The most impactful tools donât live in isolation. They connect to real-world actions and ecosystems.
đ Final Thoughts: What âGreen Techâ Should Really Mean
This challenge wasnât about who could
â Professional
Top comments (0)