Madhacks is the University of Wisconsin's twice-annual hackathon, bringing together participants from all over the US and Canada for 24 hours of hacking.
Unlike other hackathons, MadHacks is going to be putting emphasis on the wacky, the original, and the downright impossible!
$13,217 in prizes
MadHacks First Place
Nintendo Switches, or Oculus
MadHacks Second Place
Nintendo Switches, or Oculus
MadHacks Third Place
Best Diversity Hack
Most creative hack by a team that has at least 50% women
Google Smart Light Bundles
Best Beginner Hack
Free Udemy Courses of your choice
Amazon Echo Dot
Capital One Sponsor Prize
Best financial hack prize $1000
Most Viable Business Model
The Transcend Most Viable Business Model prize is awarded to the team has a project that is most likely going to succeed in market holistically. The business model, prototype, and the quality of your DevPost submission all play a factor in judging for the winner. This is the prize we believe YOU should launch a startup with. The winning team will receive chromcasts.
4 $50 Amazon Gift Card
Wolfram Alpha Award (15)
A year of Wolfram|One Personal Edition plus a one-year subscription to Wolfram|Alpha Pro.
Best use of Algolia
Use Algolia's search API in your project. Each winning team member will receive a Casio Calculator Watch
Best use of Authorize.net
Use Authorize.Net’s payment solutions (API, SDK, etc.) in your project. Each winning team member will receive an L20 Gaming Headset.
Best Domain Name from Domain.com
Register a domain using Domain.com during the weekend. Each team may submit one entry per person on the team. Each winning team member will receive a Raspberry Pi & PiHut Essential Kit.
Best use of Google Cloud Platform
Use Google Cloud Platform in your hack. Find a full list of GCP products & services at . Each winning team member will receive a Google Home Mini, max 4 per team.
Best use of HERE.com
Use HERE.com's mapping API or SDK in your project. Win gear and swag.
Best IoT Hack Using a Qualcomm Device
Use a Qualcomm device, like the Dragonboard 410C, in your IoT project. Each winning team member will receive their own DragonBoard 410C.
[Weekly Challenge] Best Chat Bot using Botkit & Cisco Webex Teams
Use the Webex Teams API or mobile SDK in your project. One winning team will be selected from all MLH Member Events each weekend. Each member of the winning team will receive a power bank.
[Weekly Challenge] Best use of Clarifai’s API
Use Clarifai's image or video recognition API or SDK in your project. One winning team will be selected from all MLH Member Events each weekend. Win hack gear.
[Weekly Challenge] Best Social Good Hack from Fidelity
Demo a project that makes the world a better place through social good. One winning team will be selected from all MLH Member Events each weekend.
[Weekly Challenge] Snap Kit Weekly Challenge
Use Snap Kit in your hack. One winning team will be selected from all MLH Member Events each weekend and top entries will be reviewed by Snap engineers. Each winning team member will receive a pair of Spectacles by Snapchat.
Submitting to this hackathon could earn you:
- Teams may have 1-4 members
- All hackers in the team must be MadHacks 2018 registered participants. We will not accept any remote participation.
- No code is written prior to the hackathon
Senior Software Engineer at DNASTAR
CEO of ThirdSpace
ECE Faculty Associate, UW-Madison
CTO of Akitabox
MadHacks Lead Deveoper
MadHacks Lead Developer
University of Wisconsin Madison
Your project will be judged on its technical difficulty and complexity. How much of the code did you write and how much of them was using an API or outside library.
Has this project been done before? If your project is to address a particular problem in society, does it actually solve that problem? Try to think out of the box and create a project that can wow our judges.
Does your project address a specific problem that we are facing in society? If not, do you think people will actually use the project that you create? Why do you think so?
Did you take into considerations some user experiences to make your project more easy to use for users?
Regardless if your project can actually run during the demo, what have you learned? What obstacles have you run into? Do you have a good story to tell about this learning experience?