{"id":8744,"date":"2016-02-25T14:12:00","date_gmt":"2016-02-25T14:12:00","guid":{"rendered":"http:\/\/mobisoftinfotech.com\/resources\/?p=8744"},"modified":"2024-11-07T17:06:49","modified_gmt":"2024-11-07T11:36:49","slug":"android-studio-2-0-beta-release-makes-developers-life-simpler","status":"publish","type":"post","link":"https:\/\/mobisoftinfotech.com\/resources\/blog\/android-studio-2-0-beta-release-makes-developers-life-simpler","title":{"rendered":"Android Studio 2.0 Beta release makes Developer’s life simpler"},"content":{"rendered":"
\n

As most of the Android developers would be using official IDE (integrated development environment) by Google for an Android app development, updates and enhancements for Android Studio does play an indispensable role in the development phase.<\/p>\n

Google has recently announced the beta version of Android Studio 2.0 as a major update coming to developers though the final release date has not yet announced. Android Studio 2.0 features can be experienced by downloading a separate Android Studio 2.0 beta version instance keeping current instance working in parallel. So one can certainly check if the new version of Android Studio resolves problem of running emulators on average or low configuration systems providing the ability to develop apps faster comparatively, ability to test on app on multiple emulators at same time to test on different resolution devices and many more.<\/p>\n

What are the new features in Android Studio 2.0?<\/h2>\n

1. Instant run<\/p>\n

2. Improved and faster emulator<\/p>\n

3. Google app indexing and testing<\/p>\n

4. Faster ADB<\/p>\n

5. GPU profiler preview<\/p>\n

6. Integration of IntelliJ 15<\/p>\n

Instant Run –<\/h2>\n

Android Studio 2.0 has enhanced cold swap feature from Android Studio 2.0 preview version to make it work in different scenarios. It allows you to do code changes and push those to the running app. This would save time to rebuild the whole application to reflect changes done no matter changes are minor or major by pushing only new changes. Depending on type of code or resource changes, instant run will swap the running application in one of the following ways –<\/p>\n

Hot swap –<\/h2>\n

Hot swap is performed when there are code changes for method implementations. App will keep running and changes will be reflected next time when method is called.<\/p>\n

Warm swap –<\/h2>\n

Resource changes (string values changes, color changes etc.) are pushed to the running app via warm swap where it quickly restarts current activity with toast message to notify developer.<\/p>\n

Cold swap –<\/h2>\n

When there is major structural changes in the code, cold swap will restart the running app to reflect changes quickly. Classes hierarchy changes, method signature changes, static initializations etc. falls under cold swap.<\/p>\n

(More details about instant run are mentioned at – \/\/tools.android.com\/tech-docs\/instant-run<\/a>. There they have mentioned about summary table for which kind changes falls under which type of swap. If we can visually designs something to show this info and here would make our blog bit different than others or by Google\u2019s official blog. Below is screenshot of summary from above link – )<\/p>\n

Improved and faster emulator –<\/h2>\n

Android Studio 2.0 beta version support Android\u2019s new emulator which is faster than earlier and more efficient for different types of apps with core Android features support. Developer can now test core features of Android APIs like pinch and zoom, multi touch events with new emulator and many more. You can set location latitude-longitude, control network settings to test your app for all use cases.<\/p>\n

Here is the brand new emulator image for Nexus 6p emulator in Android Studio 2.0 beta.<\/p>\n

Image – Android emulator side toolbar<\/strong><\/p>\n

Image – Android emulator side toolbar extended options<\/strong><\/p>\n

Google app indexing and testing –<\/h2>\n

Google app indexing helps the developer to make app searchable on Google and navigate user directly to the app content from mobile browser search results. Android Studio 2.0 beta version introduces auto code generation for app indexing implementation and tool to test app indexing feature. Testing app indexing from Android Studio will need Google account sign in.<\/p>\n

(More info on deep linking and app indexing<\/a>)<\/p>\n

Faster ADB –<\/h2>\n

Android debug bridge (ADB) is made faster by improvising processes from building the app till deploy and install on device which includes dx, Proguard, AAPT and deploy install. Faster merger algorithm to merge all dx files in the project to build the app contributes to make ADB faster. Android Studio 2.0 introduced \u201cShrinker\u201d which can be used instead of Proguard in debug or development mode still suggested to implement Proguard in release mode. Shrinker skips optimization and obfuscation steps from Proguard and just have shrinker in debug mode to make build process faster. Last but not least – AAPT, Deploy and install made faster as Android Studio 2.0 asks for deploy target even before your app is built. Faster ADB should make development easier and faster with Android Studio 2.0.<\/p>\n

GPU profiler preview –<\/h2>\n

Along with instant run, faster ADB, Android Studio 2.0 has also improved the GPI profiler preview which allows you to debug and inspect app performance frame by frame. So now graphics rich apps can be optimized from performance standpoint too. With the install of Android 2.0 beta version, if GPU profiler preview tool is not installed you can install it from SDK manager as shown in below screenshot –<\/p>\n

Integration of IntelliJ 15 –<\/h2>\n

Android Studio 2.0 is built on intelliJ 15 to make it more stable and advanced features as in –<\/p>\n