Hackathon Code of Conduct

This will be as clear as possible and applies to speakers, sponsors, and attendees. We do not want anyone to feel uncomfortable or unwelcome at the event or in the community. 


We value your participation, and if something, anything happens during the course of your participation in the hackathon that makes you uncomfortable, please make us aware of it by email or by talking directly to one the organizers at the event.  By making us aware of these situations, we can handle them in a professional manner.


We are dedicated to providing a harassment-free experience for everyone regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age, or religion. Presentations in this hackathon should not use sexualized images. Apps should not intimidate a particular social group. We do not tolerate harassment in any form.


Participants asked to stop any behavior are expected to comply immediately. Participants violating these rules may be expelled from the hackathon at the discretion of the organizers. 

We're here to help create a collaborative environment where everyone can enjoy the apps and presentations.

“Can I participate remotely?”

Yep! We'll communicate with you through email when you get the ticket. We'll stream the opening ceremony and the presentations live via Google Hangout on Air -- on YouTube.

We'll also use a Google Hangout to present across the globe. The only catch is that you would have to be ready to present at the time of the event in San Francisco, 6pm PST, June 13.

Just snag a Remote (online streaming) ticket.

“What are the prizes?”

Some hackathons have big flashy grand prizes. That's not our style. There's no better way to challenge yourself than attending a hackathon. You'll meet great people and get to push yourself.

That said we wanted to come up with prizes that can reward the good hacks. First/second/third is not the best way to judge a hackathon because oftentimes hacks are good for different reasons. So we award equal prizes to three judges' choice teams and one audience favorite.

The prizes this go around are Apple gift cards in the amount of the price for an Apple Watch Sport Band for each participant on a winning team.

Teams must be between 1-4 people.

Like we said, we've got prizes and judges, but they aren't the point of what we're achieving here. We're living on the edge and we can define the future.

"Presentations and pitches" 

You will have 30 seconds to pitch your idea at the start of the day. This is your chance to tell us what you want to work on and what roles you need to fill on your team.

Since 200 participants will be competing for glory, presentations will happen in two rounds. In the preliminary round at 6pm, each team will present to a pair of judges in a private room. The judges will pick their favorite teams to move on to the finals. Then at 7pm the finalists will present to the entire audience. Presentations are 2-minutes each and should be demos either on a real watch or in the simulator on the computer. No slides.

Our first round presentations will then be on Saturday evening. We’ll get ready for these at 5:30pm. You will see teams present back-to-back in a private room. You will select one team to move on to the finals.

The judges will be evaluating:

  1. Delight
  2. Intuition
  3. Elegance
  4. Technical mastery
  5. Compelling business potential

The finalist teams will then present in front of the whole audience. Prizes will be equal for all winners. There will be an audience favorite as well, chosen at the end.

“Can I bring code with me to the hackathon and use it in my project?”

Short look: We hold ourselves to a high standard. That means you cannot bring personal code that you've worked on previously into the hackathon.

Long look: Of course you can do whatever you want at a hackathon if you don't care about the judging process.  If you do care, then the code you bring in must be available to everyone at the hackathon prior to the start of the hackathon.  To use code you have previously written, contact uswith a link to the code and its license (which must allow others to use it) and we will update the FAQ to notify all participants of the code's availability.  Judges will take into account the use of code that has only been made available to participants very recently.  To get the highest judge's score for your project you will have to write all of your code at the hackathon and only use generally available libraries that were not created specifically for your hackathon project.  Being able to say "All the code of the demo was written during the hackathon" enables the highest scoring.

One method of achieving the highest score for your demo is to create your demonstration prior to the hackathon (or at least fight through most of the bugs and issues prior to the hackathon) and then leave all of that code at home so that the demo is (re)created from scratch during the hackathon and no old code you previously wrote is accessed during the hackathon.  The demonstration must not have previously been made public so that its disclosure at the hackathon is the first public disclosure of the hack.  By leaving the code at home or copied externally and deleted locally, you are protected from accusations that copying was performed during the hackathon. Copying code by retyping has no scoring benefit beyond that of copy/pasting code so the rules of general availability of the code, and announcement of your use of it, apply to all retyped code.

We're looking forward to seeing what can be built in such a short time. We'll do our best to publicize open source libraries that can help.

“Why charge for tickets?”

If you've been to big meetups in the Bay Area, you know that an attendee/RSVP ratio of <50% is quite common. Since we have room for 200 people, that means that we would have to allow over 400 RSVPs to account for all the people who don't show up the day of the event. And then if all those 400 people do show up, we're toast.

By charging for tickets we ensure that we all have skin in the game and we can keep the attendee/RSVP ratio more predictable. Also, after all, you will be getting good, healthy, quality food, snacks, and beer. Catering costs big money at this scale.

Reserve your ticket and show us some love :)