Android Studio for Experts (Android Dev Summit 2015)
Why Stack Overflow recommends it
Stack Overflow users link it as a reference for Android Studio tricks like live templates and keyboard shortcuts, and for how minifyEnabled and shrinkResources work.
Recommended by 4 people across 3 different months, 2015 to 2016.
What it is
A 78 minute talk from Android Dev Summit 2015 in which Xavier and Tor of the Android tools team walk through advanced Android Studio features and productivity tips. It covers shortcuts, live templates, and build topics such as code and resource shrinking.
What people said
Recommends Florin · 2015-12 · Stack Overflow · on “"minifyEnabled" vs "shrinkResources" - what's the difference? and how to get the saved space?”
The answers to the questions 2 and 4 can be found in this video from Android Dev Summit 2015 [this video] along with some other useful information on this topic. An overview of the points discussed were: shrinkResources is taken into account only if minifyEnabled is true minifyEnabled shrinks code, while shrinkResources shrinks resources that are not referenced from the code By default shrinkResources runs in safe mode. If you switch it to strict you can provide tools:keep and tools:discard flags manually to influence the resource shrinking.
Recommends Ben Pearson · 2016-02 · Stack Overflow · on “Create method on instance IntelliJ IDEA / Android Studio shortcut”
Quick answer : move the cursor to the method and press ALT + Enter . Android studio is based on IntelliJ and it's a very powerful IDE. There's lots of neat tricks that will speed up your development. For example, you could type out the code you want in your instance and then press CMD + ALT +m to extract a method. I would strongly suggest you check out this video to show you how powerful IntelliJ (Android Studio) is for keyboard shortcuts: [this video]
Recommends arne.jans · 2016-02 · Stack Overflow · on “Generate log statement from method signature”
I just saw something like that in the Android Studio for Experts Video on the Android Developers Channel: [this video] In short: You use the logm live-template at the start of your method and it generates a logging-call for the method-entry. For this you can generate the TAG -constant at the beginning of the class-body with the logt -template (the string-value will be the simple classname). Another live-template logr exists to log the method-return value at the end of the method right before the return-statement (inserted at the caret-position).
Recommends Ashish Rawat · 2016-10 · Stack Overflow · on “Android Volley always fails with Proguard”
So you can do is check the usage.txt that proguard spits and see if there is any methods that you still need and is mentioned in usage.txt. Details [LINK] Also you can use shrinkresources, more details in this vide : [this video]