DEV Community

Orbit Websites
Orbit Websites

Posted on

DEV Weekend Challenge Winners: Earth Day Edition Announced

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
Enter fullscreen mode Exit fullscreen mode

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");
}
Enter fullscreen mode Exit fullscreen mode

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)