Inspiration
We were inspired by the 305 EmpowHER Edition and the way it brings together Code Crunch Worldwide, Swift Club at FIU, GDG at FIU, ColorStack at FIU, CAHSI at FIU, Raspberry Pi Code Crunch, Hack University Worldwide, and Upsilon Phi Epsilon around one goal: helping students move from idea to working prototype. Too often, hackathon ideas stop at a slide deck. We wanted to build something that makes the “idea → prototype → live demo” path clearer, especially for women and allies across all majors.
What it does
EmpowerHer HackLab is a collaborative project hub for hackathon participants. It helps teams scope an idea, divide roles, track prototype progress, and prepare for the required live demo and submission steps.
Core features include:
An idea-to-prototype checklist that turns a broad concept into demo-ready tasks.
A team roles board for matching skills across majors.
A submission tracker for Devpost as the required submission, plus optional MLH and Kaggle challenge checklists.
A demo-readiness score so teams can see whether they have a working prototype, not just a concept
How we built it
We built EmpowerHer HackLab as a responsive web prototype using HTML, CSS, and JavaScript, with a lightweight localStorage-backed data layer so the demo works reliably during an in-person live presentation without requiring a backend. We designed the interface mobile-first, kept the language welcoming for students from all majors, and separated the checklist data into structured objects so categories can be updated for future hackathons. The readiness score is calculated in JavaScript from the three weighted inputs above.
Challenges we ran into
Scoping: We had to avoid building a concept-only presentation and focus on a working prototype with a clear demo path.
Time: Hackathon constraints forced us to prioritize the core flow: idea → tasks → submission checklist → demo readiness.
No backend: Without authentication or a database, we used localStorage and had to be clear about its limits.
Submission complexity: Devpost is required for all projects, while MLH and Kaggle are optional opt-in challenges. We had to make that distinction obvious so teams do not miss required steps.
Inclusive design: We wanted the tool to feel useful for technical and non-technical students, not just CS majors.
Accomplishments that we're proud of
We are proud that EmpowerHer HackLab is a working prototype, not just an idea. It directly reflects the 305 EmpowHER rules: every project needs a Devpost submission, a live demo, and a working prototype, while MLH and Kaggle are additional opt-in competitions. We also built a clear, inclusive interface that helps students understand what “done” looks like before the demo.
What we learned
We learned how to scope a hackathon project around a live demo, how to design for cross-disciplinary teams, and how to translate event rules into product requirements. Technically, we practiced front-end state management, localStorage, responsive design, and accessibility basics. Most importantly, we learned that empowerment is not just messaging—it is removing friction so people can actually build and present their work.
What's next for EmpowerHer HackLab
Next, we want to add real accounts and a backend so teams can collaborate across devices, build a mentor dashboard, and expand the resource library for first-time hackers. We also want to pilot EmpowerHer HackLab at future Code Crunch Worldwide events and adapt it beyond the 305 EmpowHER Edition so more students can move from idea to working prototype and live demo.
Log in or sign up for Devpost to join the conversation.