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. Read More
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. Read More
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.
This news comes about six months after Google declared the ADT plugin was no longer in active development. The change in status meant the tools would only receive bug fixes and updates necessary to remain functional, but there would be no more improvements or new features. Read More
Google I/O is first and foremost a developer conference. New products may be announced at the keynote, but just about everything is really meant for the people that build the apps. For Android developers, there are few things that matter more than their tools. Today, a fresh release of Android Studio hit the Canary channel, and it brings one of the most often requested features: C/C++ support.
Android apps, as most people think of them, are usually written in Java and have a runtime environment that imposes some additional overhead on execution. Games and other performance-critical software are usually built with C or C++ and the Native Development Kit (NDK) so that they can avoid most of that overhead. Read More
When Android Studio v1.1 entered the Stable channel, about 6 weeks ago, the Dev Tools team gave word that v1.2 was already well underway and that it would be based on the newly released IntelliJ 14. A couple of weeks later, the first preview build turned up, and it had already been upgraded to include IntelliJ 14.1, as well. Developers on the Canary channel have been testing and playing with the new features since early March, and now it's time to bring the goods to a larger audience. Android Studio v1.2 has just been released to the Beta channel with a mindboggling list of improvements. Read More
December brought us many gifts, not least of which was the official release of Android Studio v1.0. While things have been fairly quiet for developers sticking to Stable releases, the Android Tools team has been busy with a steady stream of updates for those of us on the Canary builds. After two months in development, v1.1 is finally ready to roll out to the masses. This version is mostly dedicated to bug fixes, but there are a few features added in test builds that will feel new to users that are just now receiving the update.
Changelog: (from the Android Studio 1.1 Beta post)
- Support for version 1.1 of the Android Gradle plugin (now available as a release candidate)
- Improved support for unit testing.
A couple of weeks ago, a release candidate for Android Studio 1.0 rolled out to the Canary development channel to allow users a chance to poke and prod at it before an official launch. The serious issues have been worked out and Android Studio has been given its first official release to the stable channel. Alongside the title change, Android Studio has also been declared the "official Android IDE." ADT with Eclipse is still available, but is no longer considered to be in active development.
Aside from a few bug fixes, this version doesn't contain any significant changes from the recent release candidates. Read More
It's been almost exactly 18 months since it was announced at I/O 2013, but Android Studio has finally hit version 1.0. Well, almost. This is a release candidate, so it's pretty close to what will become the first official stable release. For this release, the Android Tools team has been focusing on getting the bugs fixed and improving stability, but there are a couple of notable changes, as well.
Left: old splash screen, Right: new splash screen.
The most obvious change comes in the form of a brand new logo. Android Studio is trading out a variant of the classic bugdroid logo for a Material-inspired drawing compass. Read More
Google's recently launched Android Wear platform had a bit of a rough weekend when it ran into an unexpected snag regarding paid apps – it couldn't install them. It turns out that the behavior could be traced to a Play Store security feature that was responsible for encrypting paid apps to make them more difficult to pirate; but in doing so, it had also made it impossible to extract and install any micro-apps contained within the apk. Tuesday night, Google responded to developers with an apology and a set of steps to reconfigure development projects to circumvent the installation issue.
To implement Google's proposed workaround, developers will have to make some simple one-time changes to the configuration of their projects and then endure a couple extra steps to manually package final versions for release. Read More