Agenda Overview‎ > ‎Hackathons‎ > ‎

Develop for Good: Hackathon

Challenge: help us all be a little bit greener!
The Challenge: 
Build a way to drive real behavioral change towards sustainability by developing a tool, app or platform that rewards people for their sustainable actions (e.g. recycling, buying greener products, cycling to work, or affecting large-scale change). 

Working to build a more sustainable and clean-energy future is one of the world's greatest challenges, and something that Google cares enormously about. Change must happen at multiple levels for any positive impact to occur; from large scale fixes to industry to small, individual consumer action. These changes all add up, and consumers have a huge amount of power to drive change.

  • Google+ API (for any social / sharing integration)
  • Free2Work (obviously for calculating carbon footprints instead of human trafficking and slavery!)
  • Google Green

Office hours:
Do you need to connect with the challenge lead? You can ask a question over Google Chat or Video Chat. Simply add the email to your chat list to invite the lead to join you in a chat. Once they accept, you can communicate over chat or you can ask the lead if he is available to Video Chat (simply click on the camera icon in your chat box to initiate the video call). 

Office Hours are:
Wednesday: 8:00AM - 2:00PM PDT
Thursday: 8:00AM - 9:00AM PDT, 10:00AM - 3:00PM PDT
Friday: 8:00AM - 12:00PM PDT

Timing & submission guidelines: 
  • Hackers can start thinking about and working on this challenge before I/O but we encourage participants to take part in an Extended hackathon to complete their project.  
  • A representative from the Google Green team will be available over hangout (link to come!) and will be answering questions submitted to the moderator page. General questions will also be posted on the FAQ page.
  • In order to qualify for judging, please submit your hackathon proposal via  this form by 11:59pm (PST) on June 29, 2012.
  • 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, and the most successful team will win tickets to I/O 2013! See further details on prizes below. 
Judging guidelines:
  • 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).
  • Usefulness: does the submission allow individuals to access information that is useful to them?
  • Scalability: potential for internationalization and / or global scalability.
  • Impact: the potential for the submission to drive immediate real world impact. 
  • Design / User experience: how intuitive is the submission to use?
  • 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 during the judging process. 
The most promising submission in each challenge will be awarded the following:
  • Tickets to I/O 2013!
  • Title of 'Google Developer for Good' for 2012,  which will be featured on the Google Developer and Google Chrome blogs.  We will also provide the appropriate material to incorporate the award onto any personal websites / blogs. 
  • Mentor time with the Google Green team to work on the project through to completion.  
  • Chromebooks: there will be one additional prize of a Chromebook for the best web app submitted across all the challenges. See further details on the main hackathon page. [Note: there will only be one winner for this prize across all three challenges]
See full set of hackathon rules