Google I/O 2015 - What's New in Android Development Tools
Why Stack Overflow recommends it
Stack Overflow users link it as the official source for what Android Studio and the Gradle plugin were about to ship, especially for slow builds, SVG import, NDK support and lint checks.
Recommended by 3 people across 2 different months, 2015 to 2015.
What it is
A Google I/O 2015 session where members of the Android tools team tour what is new in Android Studio and the Gradle plugin. It covers build speed plans, SVG import, NDK support, static analysis and layout preview, with tips and tricks. Presented by Jamal Eason, Tor Norbye and Xavier Ducrohet.
What people said
Recommends Ariel · 2015-06 · Stack Overflow · on “Optimizing build time in Android Studio”
One of the most significant build time reducers is the preDex task. Check whether preDex is running in your build. It increases build time the first time you run it, but dramatically reduces build times in subsequent builds, as most of your SDKs and libraries will already be dexed. Note however that it won't run under some conditions, e.g. if you use multidex. Btw Google are well aware of build times with Gradle and Android Studio and are going to introduce significant improvements in upcoming releases, including Jack and Jill which will allow compiling from source code directly to dex. You can already try to experiment with them - see here: [LINK] . Also worth watching this video from recen
Recommends CommonsWare · 2015-06 · Stack Overflow · on “Why Gradle build is very slow for Android Studio?”
You may also want to watch the "What's New in Android Development Tools" video from Google I|O 2015 [this video] , where they discuss why the builds are slow and what is being done to improve matters in the coming months.
Recommends therobotichumanoid · 2015-07 · Stack Overflow · on “Gradle build time too slow”
The next official planned release of Gradle plugin is 1.3. If you watch the talk on gradle from a presentation at Google I/O [this video] then Google are making claims of big performance improvements. If these claims prove to be true then I believe that this will be the best chance of cutting down build times for Android projects. Currently you can use the latest beta version which is 1.3.0-beta4 by adding it to your build.gradle file. Example below: // Top-level build file where you can add configuration options common to all sub-projects/modules. buildscript { repositories { jcenter() } dependencies { classpath 'com.android.tools.build:gradle:1.3.0-beta4' } } allprojects { repositories { jcente
Cites ben75 · 2015-05 · Stack Overflow · on “Android Studio 1.3 Preview NDK support”
July 10th update Android Studio Preview with NDK support is available : [LINK] Android Studio 1.3.0-Preview is indeed available through the Android Studio "Check for updates" menu. Unfortunately, all C++ features aren't available yet in this preview. They will be available in about 2 weeks. Source : Google IO dev tools keynote [this video] at 35:38
Cites Nilesh Pawar · 2015-06 · Stack Overflow · on “Android Studio 1.3 SVG to png conversion”
In recent google IO 2015, google announced that the new Android Studio 1.3/ new gradle plugin will have support for importing and SVG file and the build system will generate the assets for different device densities (hdpi, xhdpi, xxhdpi etc): [LINK] [this video] Unfortunately there doesnt seem to be more information about how to achieve that. Does any one have any more details about it? There is some mention of it in : Android: Using SVG in res leads to error: "The file name must end with .xml or .png" [LINK] and I tried to create a hello world app and places an svg file (renamed it to xml in the drawable folder). it compiled and installed on the device, but crashed during execution saying svg is
Cites LukaCiko · 2015-06 · Stack Overflow · on “where drawable-hdpi ,drawable-mdpi ,drawable-xhdpi and drawable-xxhdpi. go?”
This is perhaps because they will add an Gradle plugin that converts SVGs to PNGs during build (as mentioned in this IO talk [this video] ). The idea is that you will only need to have a single SVG instead of multiple PNGs for various densities (an thus, only one drawable folder). You can still create the folders and use PNGs. The Gradle plugins for SVG conversion by Google has not been released yet, but you can use Victor [LINK] or a similar plugin if you already want to use SVGs for your drawables.
Cites bcorso · 2015-07 · Stack Overflow · on “Android Studio 1.3 Layout Preview Blue Print”
In the Google I/O 2015 - What's new in Android Developer Tools [this video] talk, they mention a feature in Android Studio 1.? that allows you to view a blue print of the layout preview. It is also mentioned in the Google I/O summary [LINK] page, with an example image: [LINK] Also, in the above article they state: The new visual designs haven’t quite made it into Android Studio 1.3... Does anyone know what release this feature will be available. In particular, I'm on the Beta build of Android Studio 1.3 right now. Is it currently available on any builds, e.g. Dev or Canary?
Cites thisbytes · 2015-08 · Stack Overflow · on “Android Studio v1.3 Checking for Unchecked Permissions Usage”
The following picture shows an example screenshot of the error message from the static analysis from the relevant Google I/O 2015 video. (link here: [this video] ) [LINK] And I wish to be able to run the same static analysis that will show me all of these problem areas in the app I'm working on. However, I have spent the whole afternoon running all kinds of code analysis through Android Studio with the end effect of making the code-base look so much prettier, but still coming no closer to discovering how to do what I initially sought to do. It would be great if someone could tell me how to run the static analysis in question? Thanks! Android Studio Version: 1.3 Android Studio Build Number: AI-141
Cites kycera · 2015-08 · Stack Overflow · on “Why cant i use both test artifacts in Android studio?”
In AndroidStudio different test scopes are just different flavors [LINK] . Selecting test artifact tells IDE witch flavor is test scope and because IntelliJ IDEA (on which AndroidStudio is based) does not support multiple test scopes in same module, we need to select them manually. According to What's New in Android Development Tools [this video] video from Google IO 2015. Android development tools team is working on this issue.