This article was published on May 19, 2016

Google I/O 2016: A look at how not to run a large event


lines-at-io-google

The keynote was great, the demos are cool and there’s free food and drink for everyone there — but don’t kid yourself, Google I/O 2016 is the conference version of hell.

https://www.youtube.com/watch?v=pPCk2tVU82M

Lines that span 90+ minutes, attendees being turned away at the door after waiting in said lines, and 93 degree heat with no discernible way of cooling off — aside from grabbing an Uber and bailing — are the talking points (at least amongst attendees) of I/O, not tech.

https://twitter.com/IsaacSachs/status/733076329520726018

It’s a shame.

We did witness some really cool announcements (Daydream, Allo, Duo, Android Instant Apps, Google Assistant) and some long-awaited updates (Android N, Android Wear 2.0), but all were eagerly overlooked while overheated journalists hurried to file their stories and get the hell out of there.

https://twitter.com/NateSwanner/status/733072422052581376

https://twitter.com/bryanclark/status/733072220294012929

Granted, Google can’t control the weather, but with over 7,000 attendees and a weather report that detailed dangerous heat, it could have done a little more.

Cooling stations would have been a nice start, but I think most of us would have settled for bigger venues for the side sessions, and an inkling of just how big a problem it is when journalists descend on Mountain View from all over the world to attend I/O, and then get turned away at the door for panels they’ve had lined up for over a month.

In a word, it was hell, but we’ll be back tomorrow for day two.

Get the TNW newsletter

Get the most important tech news in your inbox each week.

Thanks! Check your inbox to confirm your subscription.

By subscribing you agree to our Privacy Statement.

Also tagged with