So you didn't win a ticket to Google I/O in this year's raffle? If you're a developer, you've got a chance to be invited by Google personally to I/O this year. All you have to do is create a particularly cool Android Experiment and upload it to the challenge website. Read More
If you entered the Google I/O lottery this year, dust off your F5 keys - lotto results have started showing up in inboxes.
If you haven't received yours yet, don't worry - Google typically sends these notices out in batches. The window for registration after you receive an invite is 24 hours, so unused or declined tickets can work back into the system for the next lucky winners. And just in case you don't get a golden ticket this time, here's what the email looks like: Read More
Are you developing things with Google technologies? Can you be at the Shoreline Amphitheater in Mountain View, California on May 18, 19, and 20th? Are you willing to part with $900 for a ticket to Google I/O ($300 for students)? If you answered yes to all of these questions, you might want to get over to the Google I/O site and apply for a ticket.
Registration opened up at 9 AM PST this morning and it will remain open until 5 PM PST on March 10th, so you've got a couple of days to get your name into the pot if this isn't a good time. Read More
Google's annual developer conference is now less than 77 days away; at least that's what the new Google I/O 2016 website says. The website also says that registration begins 9AM on March 8th and goes through March 10th. As always, tickets will be in very short supply. Read More
Google CEO Sundar Pichai just tweeted the first details on when and where Google I/O 2016 will be happening. Google's annual developer conference will be taking place May 18-20th this year, but it won't be in San Francisco as it has been in recent years. It's going back to the Shoreline Amphitheatre in Mountain View, which is where the first I/O took place a decade ago.
Google releases an Android app each year providing Google I/O attendees with the schedule for the upcoming conference, and it uses the opportunity to show off how an Android app is supposed to feel. Then a couple months later it releases the source code, providing developers with a look at best practices. The source code for 2015's app has taken longer to arrive than last year's, but at last, it's here.
The Google I/O 2014 app arrived during the pre-Lollipop time when full material design wasn't yet possible on most Android devices due to the lack of the necessary APIs. Read More
Touchscreens are okay, but what about putting those pipes to better use? The description of one of Google's talks at I/O later this month points to an interesting new feature called Voice Access. Basically, instead of touching the phone, you talk to it to control apps. So essentially Star Trek? That'd be rad.
Mobile electronics use power. And as the software becomes more complex, they use more and more of it. At Google I/O 2015, the company has announced an improvement on the ultra low-power mode found in Lollipop. They're calling it "Doze," for obvious reasons, and it will debut in the M release of Android scheduled to go into a developer preview soon. It should debut in public builds later this year.
Specifics on the improvements made to the low-power mode are scarce, but apparently they are extensive enough for some dramatic power savings. According to the I/O presenter, a Nexus 9 equipped with an Android M developer preview build saw nearly two times the battery life in low power mode versus the same hardware running Android Lollipop. Read More
At the Google I/O 2015 keynote address, Google is moving fluidly between broad Android improvements for the upcoming M preview build and more specific improvements for the company's apps and APIs. One of the first reveals was for a new Chrome feature, Chrome Custom Tabs. This is basically a more robust alternative to embedding a web view in an app, adding a minimal and customized window of Google Chrome on top of the active app. Read More