Google I/O 2014 - What's new in Android development tools
Why Stack Overflow recommends it
Stack Overflow users link it when answering Android Studio questions, citing it for how projects import and migrate to Gradle, the resource-type annotation checks, and the IDE's Android view mode.
Recommended by 2 people across 2 different months, 2014 to 2014.
What it is
A Google I/O 2014 session where Jamal Eason, Tor Norbye and Xavier Ducrohet tour Android Studio and the wider Android development tools, covering what had been added since the IDE was introduced. It includes tips and tricks for getting more out of the tooling.
What people said
Recommends Eugen Martynov · 2014-06 · Stack Overflow · on “Android Studio - Difference between Import project and Open project”
I think there is no much difference if you are working with gradle project. Since Android Studio tries to sync project every time when project is opened. However there is difference if you try to import Eclipse project folder. In this case it will migrate it to gradle project structure. Watch this new IO video talk to get more about tools [this video]
Recommends Jerry101 · 2014-10 · Stack Overflow · on “Updating ADT in Eclipse causes many errors”
Some hypotheses: Broken Android SDK + tools installation. -- Can you open the Android SDK Manager and the emulator outside Eclipse? Consider reinstalling the SDK from scratch. Eclipse can't find the Android SDK + tools installation. -- Check the ADT preferences in Windows > Preferences > Android. See this screen shot [LINK] . Broken ADT plug-in or its state. -- Try uninstalling ADT [LINK] then reinstalling it. Broken Eclipse installation. -- Consider reinstalling it from scratch. This could be a good time to update to the latest Eclipse (Luna). Actually, this is a good time to try Android Studio. Right now your relative cost of switching is particularly low. Android Studio [LINK] will take g
Cites matiash · 2014-07 · Stack Overflow · on “Android Studio's "expected resource of type" checks?”
(Thanks to @CommonsWare for the heads up). There are Java annotations to support these checks in your own code. They can all be found in the android.support.annotations package: IdRes DrawableRes LayoutRes StringRes &c In this case, for example, I could use: private void mySetContentView(@LayoutRes int resourceId) { setContentView(resourceId); } and Android Studio will check that the provided resource id is indeed for a layout. Moreover, these annotations are exported, so they can be especially useful when designing a library. Sources: Video from Google I/O 2014: What's new in Android development tools [this video]
Cites sagus_helgy · 2014-07 · Stack Overflow · on “Where is Android view mode in Android Strudio 0.8.2”
I can't see "Android" line inside my menu like screenshot(this screenshot from [this video] ). My Android Studio version 0.8.2, OS Linux