If you couldn't make it to Google I/O, and thus couldn't get one of the first Android TV units as part of the developer swag, you can still start developing your apps for the platform's retail debut later in 2014. Google has included Android TV modules in the official Android SDK, underneath the Android L (API 20) package. That includes an emulator specifically for TV, so you should be able to build and test apps without any extra hardware.
All the talk about Android L this week overshadows the unfortunate fact that the previous release is still on less than 15% of Android devices. This weekend US Cellular is helping in a small way, releasing KitKat to two of its Samsung phones. The US Cellular versions of the Galaxy S4 Mini and the Galaxy Mega (6.3) are both being updated to KitKat, so those with the applicable hardware should keep an eye out for the over-the-air alert.
Let's be clear about this: developers don't have any kind of obligation to update their apps for the Android L preview release. It's a preview - by definition, it's not ready for prime time, and developers shouldn't have to immediately treat it like consumer software. That said, it's nice to see that some have already begun to prepare for the full Android L release later this year. Even relatively large players like Twitter are getting in on the action.
Basically all of Blu's phones as of the last year or so have been released with Android 4.2.2, leaving users waiting for any sign of an update to put them past Jelly Bean. We've known that the company planned on pushing KitKat to a number of devices towards the end of June, and it has now released the initial devices that will be the first to get 4.4, along with a statement on Facebook.
Android Studio was first introduced to the world a little over a year ago at Google I/O 2013. At the time, it was coined a "Developer Preview" to indicate that it wasn't ready for major development projects, but people were welcome to experiment with it. In the following months, Android Studio has progressively improved, swatting many of the bugs and adding truly valuable features for developers and interface designers. After a long, and sometimes frustrating road, the upstart IDE is finally trading in its 'Developer Preview' moniker in favor of a shiny new 'Beta' tag.
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.
As Google typically does upon the release of a new product, it has updated its support documentation with a series of common questions and issues users may find themselves facing when using Wear devices. Some are pretty handy. For example, if your phone is too far from your watch to maintain the pairing connection, you lose voice action controls. You can still set alarms, check your calendar, step count, heart rate, and a few other basic features, though.
We've already started receiving a ton of emails from concerned readers about L's app compatibility issues, broken functionality, and the like. Of course, we understand how frustrating this can be, but that's actually the point of the developer release.
One of the primary purposes behind Google releasing L for the Nexus 5 and 7 is so developers can get their apps updated before the stable version rolls out, as the switch from Dalvik to ART requires apps to be updated to add support for the latter.
The new Google keyboard in Android L brings the Material Design aesthetic to text input, but the APK pulled from L doesn't work quite right on other Android builds. It actually breaks the keyboard for most devices. No worries, though. An XDA user has tweaked it to work correctly on (probably) all Android 4.0 and higher devices. There is one method that requires root (it's actually a ZIP file) and one that might not work on all devices that's an APK.