Skip to content
This repository

TechCrunch Disrupt Public Hackathon

Saturday, May 21 and Sunday May 22, 2011

Pier 94, New York City, Google Map

Spend an intense 24 hours hacking and presenting with some of New York's brightest developers! At the end of a marathon hack session, you'll have a chance to demo in front of hundreds of audience members. A group of select judges will pick one team to present onstage at Disrupt on Wednesday, May 25th - an awesome opportunity to share the spotlight alongside the top startups chosen from Disrupt’s Startup Battlefield. More info: http://disrupt.techcrunch.com/hackathon/ and follow @hackdisrupt on Twitter for updates

To add your hack to Crunchbase

We are now adding hackers to TechCrunch’s CrunchBase to create an on-going resource of all our Hackathon activity for the development community. To create a profile for your team and hack, we’re posting a link on the wiki. One person from each team should login using their hack email address and fill out the form with team members, hack description and any content. We’ll also be linking your presentation video to this profile.

Go to: http://disrupt.brightidea.com Click “create you password” and submit your email address, create a password, and you’ll be linked to the “create your hack profile” website.

Then, follow these steps:

  1. Click "create your hack" on homepage
  2. Add your teammates and hack info
  3. Click "create your hack" button at bottom of form Some of the handwritten emails we received at registration may have been difficult to read, so please email: disrupthack@techcrunch.com if you are having issues. You can also try another team member’s email to log in. We’ll be adding your hack profiles to CrunchBase in the next couple of weeks.

Sunday, May 22

Hack presentation order

Submit your hacks before @ 9:30am

Presentations and Awards Start @ 10:30am

Submission guidelines

Display: terminating to VGA
Display resolution: 1024×768
Display settings: Mirroring turned on
Battery power: Screen Saver turned off
Battery power: Sleep mode off
Network: DHCP ethernet cable onstage, Wifi at your risk
Demo: 60 seconds
Advice: Turn off your instant messaging client if it's not needed for your presentation
Advice: Keep it brief, funny, whimsical, awesome, engaging
Advice: Practice! Run through demo w/ timer
Sentiment: We wish you luck!


Announcements

  • http://nyhacker.org will be curating an Independent Track of workshops at the event and offering hacker office hours.
  • The Design Trust will organize a group of designers who will be available for you to rope into partnering on your hacks.
  • Cool offers (Servers! Accounts!) and API Documentation Here

Schedule

More details will be announced in advance of the event - check back here!

Saturday, May 21

Doors @ 12:30PM
Kickoff @ 1:30PM

Saturday afternoon there will be developer focused workshops that last 30-45 minutes featuring:
Main Track

  • Qualcomm @ 3:10pm
  • Mashery @ 3:40pm
  • Google @ 4:10pm
  • Foursquare @ 5:00pm
  • Twitter @ 5:45pm
  • Facebook @ 6:30pm
  • TokBox @ 7:30pm

Indy NYC Track (organized by NYHacker)

  • Nodejitsu @ 3:10
  • Hyperpublic @ 3:30pm
  • Aviary @ 3:50 pm
  • GroupMe @ 4:10 pm

  • Dinner @ 7pm w/ GroupMe Fireside Chat
  • Brooklyn Museum @ 7:40pm
  • Etsy @ 8:00pm
  • Hunch @ 8:20pm

Rules

The spirit of the hackathon is to show what you can create in 24 hours on site.

  • Take something from idea to prototype in less than 24 hours
  • Submit your hack for the presentation on Sunday!
  • Demo it to everyone starting at 11am on Sunday, May 22nd. You'll have 60 seconds.

FAQ

  • Got more questions? Post them in the FAQ

Communications

Keeping in touch during the Hack Day weekend is important. Here are a few ways to make sure that you know what is going on:

Collaboration

Have an idea you'd like to share or want to pair up with others on a project? Start Collaborating.

Resources

Want to share links or information about resources (APIs, platforms, tools, etc.) that might be useful in creating projects? Start Documenting.

Something went wrong with that request. Please try again.