Get your move on! Your hack must address one of the following: improving user performance, motivating users, enhancing user experience, connecting/communicating to or with others.

 

Visit the website for more information & links to resources.

Join our Slack to stay updated (GT emails only).

 

Friday, March 2nd

  • 4PM: Registration/ Team Formation & Lunch, Klaus Atrium
  • 5PM: Dinner
  • 5:30PM: Opening Ceremonies/ Sponsor Introductions, Klaus 1116E&W
  • 6PM: Hacking Begins!, Anywhere you'd like
  • 6 - 10PM: Mentor Lounge Open, Klaus 1123
  • 7PM: Makery Workshop & Hardware Check Out Opens (Optional), Klaus 1116E&W
  • 8PM - 11PM: Makery Class Opens, CCB 337
  • 8PM: Top Time Caffeine Jolt, Klaus Atrium


Saturday, March 3rd

  • 12AM: Midnight Snack, Klaus Atrium
  • 8AM: Breakfast, Klaus 1116E&W
  • 9AM-2PM 337 Makery Workshop Open
  • 10AM-4PM: Mentors Lounge Open ~Klaus 1123
  • 1PM: Lunch, Klaus 1116E&W
  • 6PM: Project Submissions Due
  • 6:15PM-8PM: Project Expo* / Dinner, Klaus Atrium
  • 8:30PM: Top 5 Announced
  • 8:45PM-9:30PM Top 5 Final Showcase*, Klaus 1116E&W
  • 9:45PM-10PM: Closing Ceremonies and Awards*, Klaus 1116E&W

* Sponsors will announce any private level awards in addition to Grand Prizes for Software and Hardware 

View full rules

Eligibility

Participants: Must be College of Computing students (CS, CM, MS in CS/CSE, Analytics). Individuals (over 18 years in age); Teams (up to 4 students)

Requirements

  • For judging, please submit details about the project and how you built it.  Feel free to include photos, video, and a github link (if you'd like).  If your project is not fully functioning, that is okay. 
  • All submissions must be received by 6:00 PM EST, March 3rd in order to be judged.
  • After hacking finishes, teams will show their projects to each other and to the judges in our Project Expo in Klaus Atrium.  Each team will have between 2-3 minutes to demo to judges.
  • You are strongly encouraged to present a demo of what you have built. Pitches and PowerPoint presentations are discouraged.
  • You are encouraged to present what you have done even if your hack is broken or you weren’t able to finish. It's okay if you didn't finish your hack—that happens all the time! Completion is only one part of the judging criteria, so you might still do well. Also, demoing is not just about the competition, it's a chance to share with others what you learned and what you tried to build—that's what hacking's all about!
  • After the Project Expo, you may fix any bugs to your code or small fixes to your program during this time. 
  • Judges will determine a Top 5 teams for a final demo who will present at 8:45PM to judges and other hackathon participants.  Teams presenting must use their own computers.  These teams will be eligible for the CoC grand prizes.  Other company prizes will be determined during both judging rounds.

How to enter

  1. Now that your teams are officially registered, let's get started.
  2. All you need for the hackathon is a student ID, a laptop + charger, and your hacking spirit.  Check-in any hardware or tools at the registration table on Friday afternoon.
  3. You can make anything you want (app, game, etc.) that meets the requirements below, or update an existing project.
  4. Create a demonstration video and take some screenshots of your final product.
  5. Provide a way for us to access your submission for testing.
  6. Submit!

Judges

Thank you to our Sponsoring Judges for volunteering your time

Thank you to our Sponsoring Judges for volunteering your time

Judging Criteria

  • Metrics: Each scored out of 25
    Theme (25%) How well the application is built around "getting a move on". Technical Difficulty (25%) Complexity of the application Design/Polish (25%) The overall quality of the final product Innovation (25%): The originality of the concept.