Eclipse is an excellent platform that provides a great IDE for software development in Java, C++ and various other languages. Prior to Android Studio and even after, majority of developers use Eclipse as a fundamental platform for Android application development. As of this writing, the newest version was 0.2.11, Build AI-132.855830.

Android Studio has an automatic software updater that automatically checks for new updates and updates the IDE to the latest version. Android Studio is available for download from here. Android Studio uses Gradle for dependency resolution and most of the project management tasks in the IDE. Android Studio is essentially InettliJ IDEA from JetBrains, but is heavily focused on the development of Android applications.

Google announced on May 16th, 2013, at their Google I/O conference, Android Studio as their Integrated Development Environment, IDE, of choice to develop Android Applications.

To add to the confusion, there is not very many resources on the web that discusses using Android Studio for such development. A lot of documentation, books and other resources on the web discuss doing things that are centered around V1 and it is daunting for a new comer to sieve through all that and get some useful information on developing applications using API V2. Very recently Google deprecated and as of March 18th, 2013, stopped issuing API keys for Google Maps Android V1 and started recommending V2. In this article, we will try to focus on developing an Android application that uses Google Maps Android API V2, using Android Studio IDE. During the few weeks I had worked with Android Studio and with Google Maps Android API V2, I learned some lessons that are worth sharing, so that others need not reinvent the wheel and avoid the known pitfalls on their quest.

Even though I have been using Eclipse for these tasks for quite some time, Android Studio's glittering new features and ease of use caught my attention to try it out for the task. Mapping of custom hardware devices that were built with location-aware components. Recently, I was tasked with writing an application that heavily relied on GPS and

Android location services gradle