It looks like all of the recent Nexus devices are covered - everything from the 2012 Nexus 7 up through to the Nexus 5. Of course, just because branches have been published for these devices, it is not absolute confirmation that this entire list of devices will receive an official L release.
Last year, at Google I/O 2013, some major new features and improvements were announced for Google Cloud Messaging (GCM) -the replacement for Cloud to Device Messaging (C2DM). A couple of the new bits were even featured during the keynote, particularly notification syncing, which the audience loved. The one thing most people don't know is that most of the coolest things announced that year were marked as beta and locked behind an application process.
The Android team has been hard at work replacing old code that hasn't scaled well with newer and more powerful hardware. We've long known that the camera API was destined to see a massive update, but we were missing details like a release date or exactly what was coming. Thanks to the L release, we can finally see what has been in the works for all these many months.
One of the most important aspects of the new Camera 2 API is a dramatic increase in performance over the previous interface.
Android 4.4 contained a number of interesting and very powerful features for developers, many of which went unused or misunderstood for quite a long time. Since it was introduced in KitKat, The Storage Access Framework (SAF) may be one of the best examples of an API that has been underutilized, despite offering a great method to provide cleaner and more informative interfaces. I even theorized that it may ultimately take the place of file system access.
The new Google Fit Platform is a set of cross-platform APIs that developers can use to provide consumers with the means to better keep track of their fitness goals. The product intends to blend together data from multiple sources, so users can get a better overall picture of their performance and health. It empowers apps by providing them with access to a user's entire stream of fitness activity, letting software tap into data that it didn't capture itself and provide better recommendations.
It looks like Google is putting the last nail in Dalvik's coffin, and the new Android Runtime (ART) is about to take the throne. A pair of commits turned up last night in the master branch of the Android Open Source Project (AOSP) repository that spell certain doom for the Android runtime we've known
and loved for all these years. The first of the two changes completely wipes the /libdvm (Dalvik Virtual Machine) folder from AOSP, and the second takes care of changing all of the relevant configuration files and startup scripts to call on the ART runtime.
Jeff Bezos took to the stage earlier today to announce Amazon's first entrant into the highly competitive smartphone industry, the Fire Phone. Not only was the presentation loaded with some of the shiny new features of the handset and Fire OS, all meant for the press to disseminate to potential buyers, but there were also a few unusually blunt efforts to attract developers. In the midst of demonstrating Firefly and Dynamic Perspective, portions of the presentation were focused on explaining that developers would be able to extend these platform features in their own apps.
In a rare (and very amusing) fireside chat between Matias Duarte and Joshua Topolsky, we heard that I/O 2014 might put significantly more attention on great design as a topic. Today, a post on Google's Developer Blog is here to back up that declaration and adds that there will be sessions and workshops geared for designers and developers interested in improving their products. While there still hasn't been an official session list posted, this is surely meant to encourage designers to apply for registration before the window closes on Friday.