We’ve written about Android Studio a few times in the past. Google’s would-be replacement for Android Developer Tools first made its appearance at Google I/O 2013. Based on Jetbrains IntelliJ, Android Studio offers many benefits over the older ADT such as live code rendering to see how your app will look across a variety of devices and layouts, as well as the ability to easily add any Android API into your app’s code. However, the transition hasn’t been without its share of growing pains.
One such issue that has popped up isn’t an issue per se, but rather a difference in how things are done. Since Android Studio is based on Gradle-build, the way it references external libraries (such as Google Play Services) is a bit different. Luckily, XDA Forum Member JoshieGeek has already gone through the process of learning how this is done, and has shared it in our App Development forums.
If you’re a developer looking to make the switch to Android Studio but you’ve either held back due differences in external library support or have just been waiting for the growing pains to subside, JoshieGeek’s guide will likely be of use. Make your way over to the tutorial thread to get started._________
Want something on the XDA Portal? Send us a tip! -- Join us for xda:devcon 2014!