Android Studio is now the officially supported IDE by Google for Android development. This program is based on the JetBrains family of IDE's, so if you've used IntelliJ, PyCharms, or RubyMine, you'll find the user experience very familiar. Fortunately, this IDE is essentially a form of the IntelliJ Community Edition and made free for Android developers.
Android Studio uses a new build system called Gradle. The recommended approach is to directly import your Eclipse projects. In Android Studio v1.0, there is an option to "Import Non-Android Studio Project". Note that you will need to refer to the Eclipse project root directory, which should have immediate subdirectories src/ and res/. (If Android Studio does not find these directories in the project directory specified, it does not try to perform the migration to Gradle.)
When you do the import, your Java and XML resource files are relocated to src/main/java and src/main/res respectively. Gradle looks explicitly in the src/main directory and can compile successfully but will fail to include your .class files if they are not located in these particular directories.
The plugin will also generate a build.gradle. An example of what the file format is shown in the Gradle cliffnotes.
When you make changes to the build.gradle, the changes should now be reflected in the IDE. You may have target SDK versions conflicts (i.e. Facebook SDK targets for API versions above 17), so you may need to resolve your Gradle configurations to be consistent.
Android Studio should update the build.gradle file if you try to add dependencies. Any .jar files in the libs/ directory are already incorporated at compile time. You can verify this fact by opening the Gradle file for the specific module you're using:
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
}Regardless, you should keep track of what gets changed in the build.gradle since that is ultimately the file Android Studio uses to handle dependency management.
In Eclipse, Android libraries could be exported in the JAR format and added as libraries in the libs folder. With Android Studio, the option to export an Android library as a jar file has been removed. JARs had a number of limitations including the inability to include resource files within a library. With Android Studio and Gradle, "Android Archives" (or AAR files) are now the new binary format for exporting Android libraries. Android Studio provides support for export your Android library as an aar file. See this stackoverflow post for more details.
If your library is configured as an Android library (i.e. Uses apply plugin: 'com.android.library' statement in its build.gradle file), an .aar will be created automatically when the project is built. It will show up in the build/outputs/aar directory in your module's directory. You can choose the "Android Library" type in File > New Module to create a new Android Library. See this stackoverflow post for how to import local android archives into a project.
In Android Studio, you can re-create the effects of "library projects" in eclipse where you can "include" one Eclipse project as a library dependency in another project. In Android Studio, this is done with Gradle. First in the library project, change the build.gradle:
apply plugin: 'com.android.library'See example gradle file. Next, in the application to load the library, change the build.gradle file:
dependencies {
compile project(':MyLibrary')
}and in the iml file near the bottom in the last <component>:
<orderEntry type="library" name="android-support-v4" level="application" />
<orderEntry type="library" name="MyLibrary.aar" level="project" />See the sample build.gradle and iml files for reference. That should be it, after syncing Gradle the library should be accessible.
Gradle wrapper allows you to seamlessly work with multiple projects that require different versions of Gradle.
Android Studio should normally handle creating the Gradle wrapper. If you are interested in how it works under the covers, read through Gradle cliffnotes.
It's possible to choose different keyboard shortcuts from common IDEs to continue to be productive in Android Studio. Go to Apple -> Search for 'shortcuts' -> Select Keymap -> Choose from drop down.
If you're adding libraries that also define R.java resource files (such as a PullToRefresh library or Google Play Services), you cannot add them as .jar files. They must be included as dependencies. If you try to include them as .jar files, you may encounter R definitions not found during execution time.
Get familiar with the Code->Generate, Code->Reformat, and Code->Optimize Imports options. The first one will allow you to help generate getter and setter methods on your classes, saving you time from having to write boilerplate code. The other two options help to tidy up your code.
If you are using Genymotion as the emulator, you may have issues trying to use other Android SDK tools such as the Hierarchy Viewer unless you go to Genymotion ADB settings and set the path to your SDK directory (i.e. for OSX, ~/Library/Android/sdk)
You can then click on Code->Generate to SerialVersionUID:
