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
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
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
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. Our own Artem cites the ability to build both dev and production versions of apps simultaneously and the ability to use the same build process between ADT and Linux as signs that the project is already showing great potential. Read More
The contest is now over. Here are the winners, selected at random:
- Danny Holyoake
- Zhe Xi Ooi
- Marc Zdon
- Dennis F Heffernan
- Melvin Blokhuijzen
- Brett Glisson
Congratulations - you will be contacted for your information in the near future!
Everyone else - keep participating and stay tuned to Android Police so that you don't miss our upcoming giveaway announcements. You can follow AP on Twitter Facebook, Google+, and RSS.
There are a lot of integrated development environments out there, and when it comes to Android, Eclipse is one of the most popular. As always, Apress has every budding developer's back with a book written specifically for getting people up and running on the IDE. 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. The developer in me got incredibly excited and wished this tool was available years ago, because the potential time savings it brings are immense.
Basically, multi-configuration editing is a way to visualize your layout on multiple configurations at once. Read More
In a Bluetooth SIG listing (a trade certification group), LG has officially confirmed the existence of the E970 and LS970. The former is possibly headed for AT&T (it has AT&T GSM and LTE bands - which could mean Rogers as well) and is packing a quad-core Qualcomm S4 Krait chip, complete with the latest Adreno 320 GPU goes toe-for-toe with the Galaxy SIII in GLBencmark. The 1280x768 resolution is something of an oddity - why the extra 48 pixels? A 13MP rear camera and 2GB of RAM round of this beefy device's specs. It's actually quite similar to the upcoming Optimus LTE2, so we could be seeing a carrier-specific iteration of that hardware here. 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.
Note: If you already have the plugin installed, you'll need to re-install for this addition to show up.
Developers should understand what I'm talking about, but for the rest of you - this priceless little addition to our development process means whenever we want to see just what exactly Android is doing at a certain point in our programs, we can actually take a peek. Read More
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. For example, PHP has PHPLint, JSON has jsonlint and so on.
As for Android Lint, its features at launch will include the following:
- Missing translations (and unused translations)
- Layout performance problems (all the issues the old
layoutopt tool used to find, and more)
- Unused resources
- Inconsistent array sizes (when arrays are defined in multiple configurations)
- Accessibility and internationalization problems (hardcoded strings, missing contentDescription, etc)
- Icon problems (like missing densities, duplicate icons, wrong sizes, etc)
- Usability problems (like not specifying an input type on a text field)
- Manifest errors
- and many more
You can find all the current checks Android Lint performs here. 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).
Thankfully, the tools team (hi, Tor and Xav!) persistently worked on the issues and just released ADT 15 and SDK Tools 15, brining much relief to those of us experiencing said problems (the un-pausable scrolling Logcat was killing me in the last few weeks). Read More