GreenWall Challenge
Case study opening
Problem first. Solution beside it.
The starting pointA developer accountability website and app experiment built around the GitHub green wall, daily commits, streaks, reminders, and small-group pressure.
01 / Problem
Where value was leaking
Developers wanted to keep their daily coding streak alive — but no one noticed when they skipped a day, and the motivation quietly slipped.
02 / Solution
How the rebuild closed the gap
GreenWall Challenge explored a lightweight accountability layer on top of GitHub: OAuth-based contribution tracking, a happy green calendar, streak stats, achievement trophies, flexible reminders, and social pings when friends commit. The stronger product angle was “Duolingo meets BeReal” for a daily coding habit.
03 / Result
The project reached a clear validation point: 32 people joined the email list and the technical foundation existed, but the scorecard showed weak monetization, low defensibility, and a crowded market of free streak tools. It was canceled as a revenue bet and kept as a focused build-in-public / portfolio experiment.
