Android has gone through quite a few changes during its short 6 years of life. The Android that drives most of the world's smartphones of today would be almost unrecognizable to what was launched in late 2008. We've seen massive visual changes, expansion to almost every conceivable form factor, and a completely fleshed-out content ecosystem for multimedia and apps. As the operating system matured, some elements have successfully grown with it, and others have become dead weight.
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.
In preparation for the upcoming final releases, the Android team today released ADT 17-preview (Android Developer Tools plugin for Eclipse) and SDK Tools r17-preview with the following improvements that eager developers can try out without waiting any longer.
Out of all the additions and changes, I'm mostly excited about the new network usage tool, the fix for the dreaded "Conversion to Dalvik format failed with error 1" error when trying to use Proguard (oh, how many hours I wasted on this one), and the end to default ids for various layout elements.
After we blew the faults behind Google's License Verification Library out of the water last week, Google's Tim Bray promised us some tips for protecting our applications against piracy, and in the latest post at Google's official Android blog he delivered them. Tim's article is loaded with easy to follow sample code, and advice that just makes sense.