One of the biggest challenges to creating good apps for Android Auto has been actually testing the experience. Many independent developers can't afford to purchase brand new cars with Auto built-in, and aftermarket head units won't fit in most recently manufactured cars without heavy modification, and most of those units aren't very good anyway. When the Auto SDK came out, it included simulators that could be used for basic testing of just the messaging and media browser interfaces, but even these weren't good substitutes for the real thing. Today, Google released the Android Auto Desktop Head Unit, a functioning implementation of the Android Auto platform that runs right on a desktop or laptop.
It has been almost a month since Google Play services 7.8 began rolling out to users, and as of yesterday, it is in wide release to everybody. A previous blog post by Google discussed the big new feature for developers would be the Nearby Messages API, but it turns out there are a couple of other additions worth checking out. In a new post on the Android Developers blog, Google announced a new Mobile Vision API with the ability to detect the presence, orientation, and some details of faces when they are in frame on an active camera.
With the official stable release of Android Studio v1.3 a couple of weeks ago, it's time to begin testing the next string of new features. The first preview release of version 1.4 is now in the Canary channel, and it's sporting some big new features. The Android Tools team has been working on the new theme editor first demonstrated in the I/O session titled What's New in Android Development Tools. There are also new performance monitors for GPU and network activity, a vector asset wizard for turning SVG files into XML vector drawables, and a few new lint checks.
Here is the Google I/O session video cued up to the beginning of the theme editor demo at 36 minutes:
The new theme editor examines the styles in a project and displays visual samples of what controls should look like on a live interface.
Game developers have a new player in the game engine market, and it's one most of them already know quite well: Autodesk. At GDC Europe, the software company behind some of the most popular 3D modeling tools in the industry – 3ds Max and Maya – has announced the Stingray game engine to compete with the likes of Unreal, Unity 3d, and others. Alongside Autodesk's other design tools, it offers a seamless solution for game developers and designers to rapidly prototype and build high performance, cross-platform games.
Stingray is based on the Bitsquid game engine acquired by Autodesk last year. It supports testing and deployment to Android, iOS, Windows 7 and 8, Oculus Rift DevKit 2, PS4, and Xbox One.
The new Android platform version distribution numbers are up on Google's developer site, and given no data was published during the month of July, that means we've got two months of change. Lollipop continues to climb - it's up from 12.4% a full 5.7 points, now at 18.1% of all devices. KitKat actually hasn't lost much traction because of that, and actually grew a tenth of a point, now at 39.3% of all devices versus 39.2% two months ago.
Android version stats, August 2015
Previous data (%)
Current data (%)
The real loser is Jelly Bean, down 3.8 points, with Ice Cream Sandwich down 1, Gingerbread down 1, and Froyo hanging steady at 0.3% (diediedie).
Microsoft surprised Android developers last year with the launch of a brand new emulator designed for performance and features that aren't available anywhere else. While the initial Preview release only included an image for KitKat, subsequent updates introduced an expanded set of emulator images and some valuable new features. While a high-speed emulator is certainly compelling, many developers still didn't adopt it because it had to be downloaded and installed alongside a very large Visual Studio package, not to mention it was also frustrating to set up for use with other IDEs. Last week, Microsoft unburdened the emulator and released it as a standalone download along with step-by-step instructions to set it up to easily run with Android Studio and Eclipse with ADT.
A large part of the What's New in Android Development Tools session at Google I/O 2015 focused on one particular feature, or rather, group of features coming to Android Studio: upcoming support for C/C++ and the Android NDK. Version 1.3 RC1 of the IDE hit the canary channel late yesterday, finally enabling developers of native apps and games to begin transitioning from Eclipse (or another IDE) to Android Studio, if they choose to. Functionality is described as "preview quality," so there are still some known issues and probably quite a few bugs.
With the addition of NDK support, this release brings a number of internal and organizational changes, some of which will affect all developers.
It's been a long and winding road, but the days of Eclipse with ADT are over. In a post on the Android development blog, Google has announced that development and official support for the Android Development Tools plugin for Eclipse will be shut down at the end of this year. Google intends to focus all of its effort on improving Android Studio and advises developers move their active projects to Android Studio using the included migration tool.