What to Build for Hackathon

Participants are tasked with building an innovative and functional software project that aligns with the prompt provided on the day of the event. Teams should focus on identifying a problem, brainstorming potential solutions, and then rapidly developing a proof of concept or working prototype. Projects can vary widely, and can be anything from a mobile app to a 2D-multiplayer game. The essential requirement is to maintain a clear connection between the software and the prompt, addressing a specific problem identified by your team.

In addition to programming the project, hackathon participants must also prepare a short presentation (no longer than 3 minutes) to deliver to the judges. This presentation should highlight the problem your team has identified, the solution developed, its relevance to the prompt, and its potential for positive impact. It is also recommended to include a segment detailing individual team member roles and dynamics, as collaboration will be evaluated. Presentations will be conducted individually, however winning teams will also be asked to give a short pitch of their product to the audience.

After presenting to the judges, teams should conduct a short product demo and provide an explanation of how the software was built and what technology was used. Teams who are unable to complete their project are encouraged to present a Figma or another visual representation of the intended design and functionality during the product demo. Demonstrated planning of the design of the software, even without full implementation, may count towards points in the Design and User Experience category of the rubric.

What to Build for Ideathon

Participants are tasked with developing a comprehensive proposal for a software product that addresses the given prompt. Teams should aim to identify a clear problem or need, conduct thorough research, and ideate potential solutions. While the actual creation of the product is not required, Ideathon project entries should feature well-thought-out plans for both implementation and business strategy. In place of being judged on Technical Execution, these projects will be evaluated on Feasibility and Marketability, necessitating thorough planning.

During the judging period, teams must deliver a presentation on their product lasting no longer than 6 minutes. This presentation should cover the problem identified, the proposed product solution, plans for implementation, and strategies for reaching the target audience. It is also recommended to include a segment detailing individual team member roles and dynamics, as collaboration will be evaluated.

Ideathon participants will also be expected to create a basic mockup of their product’s main design to be exhibited during or after the presentation. This mockup can be made using Figma, InVision, Canva, or another digital design tool, and will count towards the Design and User Experience category of the rubric.

What to Submit

Both streams must submit all finished work to Devpost by 11:45 AM on August 20th, with a 15-minute grace period. This includes the final product presentation for judges, as well as any files or photos of design mock-ups intended for display. Hackathon participants must also provide a link to the project’s source code, preferably hosted on GitHub.

Submissions to Devpost must include completed project description sections, detailing the purpose and functionality of your project, the technologies used, and the challenges your team overcame. Additionally, it is recommended that participants fill out member roles after submission to contribute to the Collaboration section of the rubric.