Happy Google I/O 2012!
I believe in having a sense of humor in everything that you do…and that you can’t please them all. We improved registration over last year, but will always have more to do and learn. In the meantime, I thought this was an excellent way to channel your energy into something positive…it certainly made me smile :)
I had no idea input/output would take on such a life of its own. When I first briefed our agency, I wanted a concept that would give our Google developers a way to get to know each other and build a community in the months leading up to I/O. Last year’s countdown was a crowd pleaser for sure, but I thought, with thousands of developers hitting our site, couldn’t we use that momentum to build something bigger than the sum of its parts?
We figured that since developers express themselves through building apps, why not give them a new platform to learn with its own tools, logic and idiosyncrasies.
With any type of UGC-dependent campaign, we had no idea what the response was going to look like (and just because we’re Google, it doesn’t mean our ideas are always successful). But in this case, I think we were able to tap into a familiar paradigm for our audience and deliver an experience that spoke to them.
I hope that our Google developers will excuse my marketing speak for the time being. My coding skills are pretty limited, though doesn’t writing SQL queries, pushing to Git and being able to reminisce about l33t, Tetrinet and mIRC count for anything? :P
Anyways, all of this is really just to say here are some of the most memorable machines, just one week after launch.
In addition to the new tech and highly sought after freebies available at Google I/O conferences, the company has made a habit of kicking off the conference with the introduction of a cool new online toy.
This year’s no exception. Check out this year’s Chrome Experiment, a fun digital pinball machine-like assembly kit called Input/Output. For the best results, run it on Chrome (naturally) and get set to lose a few hours like we did this morning, as the screenshot of our machine below attests.
It gets increasingly hard to feel like you’re making an impact when you’re at a company that grows by the hundreds each day, but mentions like this make me feel like I’m doing something right.
Field-side at Triple’s Alley to celebrate an I/O well done with the team.
A and I were confirmed together in high school…we were the oldest kids at Catholic school. Eight years later, he found me on the Google blog and we reconnected at I/O.
We all love a good Easter egg here at Google. Now if only the internet archive could resuscitate geocities.com/kittiepawz. Sigh…
Flashback: When I joined the Google I/O two-man team back in December 2010, we were in desperate need of a site and I had one month to update the content here. Maybe I was driven by a desire to make my day job more interesting, but I wanted the site to inspire in the same way that our technologies, speakers and demos did at the physical event. And that’s what it took to deliver this year’s countdown: one woman who didn’t want want to be bored 8hrs a day :)
Here’s a behind the scenes peak at the creative process. We started with the idea of running a countdown in the final run to I/O. The first designs came back overly designed…they were too abstract and I didn’t think they’d appeal to developers.
So I asked the team to take a step back. I wanted the countdown to be a paradigm of how time is normally represented. A v.1, v.2 and v.3 later, we had a design comp that we were happy with!
Analog session scheduling for I/O. We haven’t figured out an algorithm for this one yet.