Develop for Good: Hackathon

In conjunction with this year's I/O, we will be hosting a Google Develop for Good Hackathon. The 'open source' hackathon will be open to all I/O Extended attendees and we highly encourage Extended organizers to consider incorporating a hackathon into their event agendas, and focusing on these challenges!  The 'Develop for Good' challenges have been created by teams at Google that truly believe that technology can used to address global challenges and drive real social impact. 

If you are planning to participate in the Google 'Develop for Good' hackathon, please let us know which event you are organizing and the timing of your hackathon so we can send you some stickers, and try and make sure our challenge experts our available over hangout / moderator. Please email to register interest. 

Click the buttons below to find out about each challenge, and further down the page for general details around the hackathon. 

The Challenges


The Hackathon

  • Hackers can start thinking about and working on a challenge before I/O but we encourage participants to take part in an Extended hackathon to complete their project.  All hackers should submit a solution to one of the challenges by 11:59pm on June 29, 2012. 
  • We will be hosting a 'Develop for Good' hackathon in the San Francisco Google office  June 28th - 29th, from 9am - 5pm PST on each day, however each extended is free to organize their own hackathon around whatever time frame works best. Before the beginning of I/O we will embed an introductory videos for each challenge on the challenge page, which organizers and hackers can also play at their convenience. 
  • Over the duration of I/O, hackers will be able to ask general questions about the hackathon on the FAQs page, and direct specific questions around each challenge the Google challenge experts on the specific moderator pages.  The Google challenge experts will also be available over hangout during the hours of the San Francisco hackathon. Details will be posted on the individual challenge pages. 
Submission & general guidelines:
  • Unless specified, hackers can use any platform or tools to address the challenge, however we obviously encourage the use of Google products and APIs! :) There will be a separate prize from the Chrome team for the best web app developed, but this shouldn't be a distraction to solving the task at hand! Examples of products that might be relevant include; Android, App Engine, Google+, Chrome and Google Apps. You can find info about many more products and platforms on the Google Developer site. 
  • Though the challenges are in English they are open to hackers all over the world. Critical parts of submissions should be in English, as we unfortunately will not have the capability to translate anything. 
  • Any branding included on a submission should be created by the individual / team who worked on it -- no reference to Google branding should be included. 
  • In order to qualify for judging, please submit your hackathon proposal via this form by 11:59pm (PST) on June 29, 2012.
  • Submission should include a link to a solution, whether it be a mobile or web app, website or platform, and a short text description of the proposed solution. Any necessary instructions should also be included. 
  • Submissions will be reviewed by a judging team of Googlers following 06/29/2012 and we hope to announce the most successful projects by 08/01/2012. 
  • Once the judging process has been completed we will feature the most successful hacks on the Google Developers blog. The most successful team in each challenge will also have the chance of winning a tickets to  I/O 2013!  
  • See challenge-specific guidelines on the individual challenge pages. 
The most promising submission in each challenge will be awarded the following:
  • Tickets to I/O next year!
  • Awarded the 'Google Developer for Good' for 2012,  which will be featured on the Google Developers blog and Google Chrome blog. 
  • Mentor time with the challenge team (e.g. Google Ideas, Google Politics & Elections) to work through the project.  
  • The most successful teams will be announced ~08/01/2012.
In addition, the most successful web app across all submissions will be awarded Chromebooks (see further details below).

Please see individual challenges for judging criteria but all three will be judged according to the following: 
  • Originality and creative approach: to solving the outlined problem, along with actual demonstrated solution for the problem.
  • Functionality: working functionality of submission as submitted, without further demonstration, and the potential for the submission to be completed through to launch (this will also take into account demonstrated technical capabilities).
  • Scalability: potential for internationalization and / or global scalability.
  • Impact: the potential for the submission to drive immediate real world impact. 
  • Design / User experience: for intuitive use of app, platform, website.
  • Accessibility: for example, how accessible a website is to a screen reader. See further guidelines at the following resources:
  • Social: Any integration with Google+! 
  • Critical parts of submissions should be in English, as we unfortunately will not have translation capabilities.

Additional prizes

Chrome Web App Prize: 
Across all the challenges we will also be awarding a prize for the best web app submission, in collaboration with the Chrome team. 

  • Chromebook & Chrome T-shirt 
  • The webapp should be built entirely with HTML, Javascript and CSS. 
  • No Flash, Java or other platforms should be used (though exceptions might be made for the use of audio) and the app should not depend on any plug-ins. 
  • Desirable features include the following: 
    • WebGL or Accelerated Canvas2D, SwiftShader, Web Audio, Intents, Offline capabilities, CSS Transforms and Transitions, Power-friendly (requestAnimationFrame and friends), Social / Connected (eg WebSockets), Native-like features: fullscreen, mouselock, notifications, geo, orientation, speech etc
    • Performance using WebWorkers or even NativeClient
    • Tested for Accessibility, I18n & ChromeFrame
    • BoxModel or grid for layout
    • Works on ChromeOSWorks on Chrome-on-Android
See full set of hackathon rules and the general  FAQs page.