Inspiration

After participating in a hackathon and not winning, I wanted to understand why my project didn't make the cut. While I received feedback from some judges, I realized that there wasn't a consistent way to provide or receive feedback on hackathon projects.

What it does

To address this issue, I propose adding a section to the hackathon platform for judges to leave private feedback on the projects they reviewed. This feedback section would not be visible to the public, and instead would only be accessible to the developers of each project.

The feedback would be helpful for developers to know what they did well, what they could improve on, and how they could approach future hackathons differently. Even if a project doesn't win a cash prize, the developers would still receive a valuable review from another developer who took the time to look into their project.

Other thoughts

In addition to the feedback section, I suggest including a section for tangible prizes like swag. This would incentivize more people to participate in the hackathon and could create a sense of community among participants.

While I understand that many hackathons already offer external KYC to ensure that prizes are sent to the correct person, having a section for the host to send tangible prizes would be an added bonus.

Overall, I believe that adding a feedback section to the hackathon platform and a section for tangible prizes would be beneficial to all parties involved. It would create a more transparent and supportive environment for developers and judges alike, and would encourage more people to participate in hackathons.

Constructive criticism

The filter and sorting for the project gallery is kind of broken if your trying to filter projects for certain prize tracks. I suggest adding "winners" to the selector component for sorting.

What's next for Devpost Hackathon Developer Feedback

I can help build it?

Built With

• words