Submission Requirements What to Build

Build anything that showcases innovation, creativity, and technical skill! Your project should be:

• Started and completed during the hackathon (no pre-existing projects)
• Functional - at minimum, a working prototype or demo
• Original - your team's own work

Project Ideas by Track

You can build for any or all of these categories:

General Categories:

• Any innovative software project
• Web apps, mobile apps, browser extensions
• Games, creative tools, productivity apps
• Hardware hacks (if you have the equipment)

Best Rookie Hack:

• Perfect for first-time hackers
• Focus on completing a working project, even if simple
• Show your learning process and creativity

Best Social Good Hack:

• Projects that make a positive impact on society
• Address real-world problems (accessibility, education, environment, health, etc.)
• Consider underserved communities or pressing social issues

Best Use of Google Gemini API:

• Must integrate Google's Gemini API in a meaningful way
• Use AI Studio or Vertex AI environment
• Showcase creative or impactful use of generative AI

Best Use of MongoDB:

• Must use MongoDB Atlas in your project
• Demonstrate effective database design
• Can be combined with other technologies

What to Submit

All submissions must be completed by 7:30 PM and include:

Required:

1. Project Title - Clear, descriptive name for your project

2. Description - Explain what your project does and the problem it solves

   • What does it do?
   • Why did you build it?
   • What problem does it solve?

3. Technologies Used - List all tools, APIs, frameworks, and languages

   • Be specific (e.g., "Google Gemini API for text generation, React for frontend")
   • Include any AI tools you used to help build it

4. Track Selection - Choose which category/categories you want to compete in

   • You can select multiple tracks!
   • Each track has its own judging criteria

5. Working Demo - At least one of the following:

   • Link to live deployed project
   • Video demonstration (2-3 minutes recommended)
   • Screenshots showing key features
   • GitHub repository with clear README

Strongly Recommended:

1. Demo Video - A short video (2-3 minutes) showing:

   • Quick intro to the problem
   • Demo of your project in action
   • Key features and how they work
   • Technologies you used

2. GitHub Repository - Include:

   • Clean, documented code
   • README with setup instructions
   • List of dependencies
   • Any necessary API keys should use environment variables (don't commit secrets!)

3. Screenshots - Show off your UI/UX

   • Main interface
   • Key features
   • Before/after comparisons if relevant

Optional but Impressive:

1. Presentation Slides - If you want to present during demos

2. Future Plans - What would you add with more time?

3. Challenges & Learnings - What did you struggle with? What did you learn?

4. Team Information - Who did what on your team

Submission Tips

✅ DO:

• Start your Devpost submission early (don't wait until 7:25 PM!)
• Test your demo/video before submitting
• Proofread your description
• List all team members
• Be honest about what works and what doesn't
• Show your process and learning

❌ DON'T:

• Submit pre-existing projects
• Violate any API terms of service
• Include sensitive information (API keys, passwords, etc.)
• Plagiarize or use others' work without attribution
• Wait until the last minute to submit

Technical Specifications

Hosting & Deployment:

• Use any platform: Vercel, Netlify, Heroku, Google Cloud, Replit, etc.
• Make sure your demo is publicly accessible (or include login credentials if needed)

Video Format:

• Upload to YouTube, Vimeo, or Loom
• Keep it under 5 minutes (2-3 minutes is ideal)
• Make sure it's publicly viewable

Code Repository:

• GitHub, GitLab, or Bitbucket
• Must be public or accessible to judges
• Include a clear README with setup instructions

Judging Focus

Judges will evaluate based on:

• Innovation - How creative and novel is the idea?
• Technical Execution - Does it work? How well is it built?
• Design & UX - Is it user-friendly and well-designed?
• Impact - Does it solve a real problem? Who benefits?
• Use of Technology - How effectively are tools/APIs used?
• Presentation - How clearly is it explained and demonstrated?

 

Different tracks may weigh these criteria differently. See the "Rules" section for specific judging criteria per track.