Google I/O, one of the most exciting conferences of the year for us, has come and gone. From sleeping several hours a day to juggling about seventeen things during the live keynote coverage to suddenly finding ourselves within inches of people like Sergey Brin, Sundar Pichai, Lord and Savior Matias Duarte, Hugo Barra, Vic Gundotra, Robert Scoble, Chainfire, Saurik, and other brilliant Googlers, reporters, and developers, the days spent at every I/O are absolutely priceless.
Yesterday Google launched an early access preview of Android Studio, an integrated development environment (IDE) for Android based on IntelliJ IDEA. This one-stop shop for coding, compiling, and testing includes all the standard Android SDK tools, plus build support, quick fixes, tools to catch major coding flaws, and a preview window. The Android Developer Tools session at Google I/O went into massive detail on the new project. The 53-minute session is embedded below, in case you couldn't make it.
Even if you're not physically attending Google I/O, the official convention app might serve you well. It allows attendees to scan badges, view schedules, and just guide themselves around with vector-based maps. If you're not going to be in Moscone Center tomorrow, you can stream sessions with the app. Waiting just about as long as possible, Google has pushed an update to the I/O app, and it adds some cool stuff.
Welcome back! Google Play Services 3.1 is such a ridiculously huge update; I had to stretch it out over two articles - that's a first for APK Teardown. If you somehow missed the Google Play Games extravaganza, part one is right here.
Part two is all about the non-games discoveries, which there are a lot of. Before we get into that though, there is one detail I left out of the games article that I really should mention:
The Play Games Codename
Google always comes up with the coolest code names for projects, and the Play Services games client is no exception.
If you're in the small portion of the Venn diagram where Google Ingress players and Google I/O attendees intersect, I'm about to make you very happy. It looks like the big G is paying quite a bit of attention to Niantic Labs' social geo-game, because every single registered attendee for Google I/O 2013 will be given an automatic invitation to Ingress, which is still in beta. Ingress will also be given at least some coverage in the initial I/O keynote on May 15th.
Google just updated the sold out I/O 2013 conference website with the full schedule developers have been dying to see for months, ever since the initial announcement back in February. During the three days in mid-May (May 15-17), the company's engineers will host over 120 talks on such topics as:
- Chrome & Apps
- Google Cloud Platform
- Knowledge & Structured Data
- and other tech subjects
On day 3, developers will also be able to participate in Code Labs on the topics of Android, Google+, Chrome & Apps, Google Cloud Platform, and YouTube.
As everyone is trying to guess whether the next big Android update is going to be Key Lime Pie or not, and whether the release will be Android 5.X or 4.X, we have yet to hear anything concrete. After getting a tip from an eagle-eyed reader (thanks, deepayan!) and digging deeper, I can definitively tell you that Google is currently working on Android 4.3, and it is still Jelly Bean.
You got your Google I/O ticket. Hotel's booked. Flight's reserved. For all intents and purposes, you're ready for Google I/O 2013. If you need something to do the evening before the event starts, however, Lookout's got you covered. Well, kinda. Lookout has 20 of you (plus one guest each) covered.
Of course, we're talking about Lookout's annual Google I/O Party. Here's the skinny: every year, Lookout holds a pretty killer party for Google I/O with free drinks, food, and giveaways.
The day is here, boys and girls – I/O 2013 registration is open! Even at $900 a ticket ($300 for academic attendees), they sold out in 25 minutes last year. We expect the same thing to happen this year, so if you want to go, hopefully you waited until after you picked your ticket up to read this post.