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. Read More
Looking to create a more versatile and powerful build system for Android developers, Google has been working on what is currently called "New Build System," a tool that aims to (one day) replace, unify, and build upon the functionality of Eclipse's ADT and Ant build systems.
While the new build system is still in very early stages (just reaching build 0.1 today) and not yet ready to build ship-able apps, it's already proving useful. Read More
For some time, Motorola Mobility has offered its MOTODEV Studio for Android suite as a standalone alternative build on Eclipse. A lot of developers seemed to like the additional tools Moto built into Studio, but weren't exactly keen on dropping Eclipse in exchange for Moto's less open solution.
Now that Motorola is a part of Google, it seems that state of affairs just won't do. Earlier today, on the official Motorola blog, the company announced it was open sourcing key parts of MOTODEV Studio and merging them into the Android Open Source Project. Read More
The Android developers' tools team, headed by the usual suspects Xavier Ducrohet and Tor Norbye, led a session at I/O 2012 today dedicated to improvements and new features coming to the tools devs use to make apps - ADT for Eclipse and SDK Tools.
Everything they showed took around an hour of nonstop talking, arm flailing, and cracking jokes about the French, but among all the new goodies one prominently stood out - multi-configuration editing. Read More
Coinciding with the announcement of Android 4.1 Jelly Bean, Android developers can now pull down a new revision of Android's SDK tools – revision 20, along with a new version of the ADT Plugin, also r20 (which Eclipse users will need to use SDK r20).
The revised SDK tools bring several improvements. One of the notable additions to the SDK tools is System Trace (otherwise known as systrace), a tool (included in Project Butter) that helps monitor system activities, allowing developers to pinpoint graphical rendering or other issues. Read More
As an Android developer, I like to keep tabs on the tools I use every day, especially ones as important as ADT for Eclipse and SDK Tools. As was the case several times before, the Android team in charge of both of them posted previews of upcoming releases of ADT 20 and SDK Tools r20, available for manual download ahead of the final releases.
Yup, you heard me correctly - 20, not 18 or 19. Read More
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. Read More
As an Android developer, the first thing I do when I set up Eclipse with ADT on a new machine is hunt down the Android source for the API level I'm working on.
Earlier this month, I added a request for Android 4.0
source to be added to the plugin, and I'm pleased to report that the plugin maintainer just added it to the latest version.
Honeycomb sources are being worked on.
To help Android developers automate some things and catch certain errors early on, the Android Tools team is pushing ahead with a new dev tool called Android Lint. Android Lint will be available in the next release of ADT (16) and Tools (r16).
If you're not familiar with the "lint" paradigm, a lint tool generally helps you validate your code using a certain set of rules in order to avoid common pitfalls. Read More
The Android 4.0 API that was released together with the unveiling of the Galaxy Nexus also brought us, developers, ADT 14 and SDK Tools r14, which quite a few people started having problems with almost immediately. The tools were released in an incomplete state based on my experience with ADT 14-preview, as some serious and known bugs weren't fixed when 14-final came out. I have a feeling the ICS event kind forced the corresponding ADT/tools 14 release and prompted Google to roll it out in what I consider a broken state (many reported crashes, broken Logcat, etc). Read More