Google has released the latest version of Android Studio with over 20 new features including some relating to the ‘Pie’ release of the OS.
Among the major new features is support for ‘App Bundles’ which is Google’s new way of packaging Android apps to shrink their size.
Google’s research has found the larger an app is, the fewer installs it receives. Size reductions achieved by using App Bundles vary but Twitter saved 35 percent, Jomo saved 50 percent, and LinkedIn saved 23 percent.
The next major feature is ‘Emulator Snapshots’ which builds upon ‘quick boot’ to boot up and return to a snapshot preconfigured with the correct settings in under two seconds.
No user likes a dead battery, so if your app is found to be the culprit, it’s not going to win you any favors. A new ‘Energy Profiler’ allows you to visualize the estimated energy usage of system components, plus inspect background events that may contribute to battery drain.
The major addition for Android Pie users is support for ‘Slices’ which allows users to surface app content in Google Search suggestions and the Google Assistant.
Other Features Include:
This feature allows you to use placeholder data to aid in the design of your app. This will help you visualize layouts that depend on runtime data. You can add built-in sample data to populate views such as RecyclerViews, ImageViews, and TextViews via a popup window in the Layout Editor.
Material Design Update
When you start migrating from the Android Design support library to the new MaterialComponentsapp theme and library, Android Studio 3.2 will offer you access to new and updated widgets such as BottomAppBar, buttons, cards, text fields, new font styles, and more.
CMakeList Editing Support
For those using C/C++ in its app, Android Studio has better support for CMake. With this release of Android Studio 3.2, code completion and syntax highlighting now work on common CMakeList build script commands.
What’s New Assistant
Android Studio 3.2 has a new assistant panel that opens automatically after an update to inform you about the latest changes to the IDE. You can also open the panel by navigating to Help → What’s New in Android Studio.
AndroidX Refactoring Support
One of the components of Android Jetpack is the introduction of the Android extension libraries (AndroidX) as a replacement for the Android Support Libraries. To add AndroidX to a new project you just need to add android.useAndroidX=true to your Gradle. properties file. Additionally, Android Studio 3.2 has a new built-in refactoring action to help migrate your project to the new namespace and dependencies. Also if you have any Maven dependencies that have not migrated to the AndroidX namespace, the Android Studio build system will automatically convert those project dependencies as well.
IntelliJ Platform Update
Android Studio 3.2 includes the IntelliJ 2018.1.6 platform release. This IntelliJ release adds many improvements to data flow analysis, debugging, new inspections, inline external annotations, partial Git commits, plus much more.
Android Studio 3.2 bundles Kotlin 1.2.61, with support for the Kotlin-friendly Android 9 Pie SDK.
In some cases, new Java Language features require new bytecodes and language APIs. However, older Android devices may not support these features. Desugaring allows you to use these features on older devices by replacing new bytecodes and language APIs with older ones during the build process. D8 desugaring is turned on by default for Android Studio 3.2 and you can now use most of the latest language changes while targeting older devices.
Starting with Android Studio 3.2, we are starting the transition to use R8 as a replacement for ProGuard to optimize and shrink Java language bytecode. R8 is still experimental, so we do not recommend publishing your app using R8 yet, but it is a good time to give the Android Studio team early feedback so we can make any adjustments before R8 fully replaces ProGuard.
Microsoft® Hyper-V™ Support
You can now run the Android Emulator on Windows® 10 computers that have Hyper-V enabled. Intel HAXM is still the default hypervisor for the fastest Android Emulator experience. However, thanks to recent open-source contributions by Microsoft, and the addition of the new Windows Hypervisor Platform (WHPX) API, the Android Emulator can coexist with other Hyper-V-backed applications, like local Virtual Machines, using the new Hyper-V Support.
AMD® Processor Support
AMD Processors are now supported by the Android Emulator on Windows 10. Previously running the Android Emulator was limited to slow software emulation when running Windows, but developers who have an AMD processor can now have hardware accelerated performance.
Screen Record in Android Emulator
You can now record both screen and audio on any Android API level with the new screen record feature in the Android Emulator. In the past, screen recording on a physical Android device only worked on Android 4.4 KitKat (API 19) and above with no audio, with limited Android Emulator support. With the latest Android Emulator (v28.0.+) you no longer have this restriction. As a bonus, there is a built-in conversion to output to GIF and WebM. You can trigger the new screen record feature via the Android Emulator Extended Controls panel, command line, and from Android Studio.
Virtual Scene Camera for Android Emulator
The new Virtual Scene camera in the Android Emulator helps you to develop for ARCore, Google’s platform for building augmented reality experiences. The emulator is calibrated to work with ARCore APIs for AR apps and also allows you to inject virtual scene bitmap images. The virtual scene camera can also be used as a regular HAL3 compatible camera.
ADB Connection Assistant
Android Studio 3.2 has a new assistant system to help troubleshoot your Android ADB device connections issues. The ADB Connection Assistant walks you through common troubleshooting steps to connect your Android device to your development machine. You can trigger the assistant from the Run dialog box or by navigating to Tools → Connection Assistant.
The new System Trace feature in the CPU Profiler allows you to inspect how your app interacts with system resources in fine-grained detail. Inspect exact timings and durations of your thread states, visualize where your CPU bottlenecks are across all cores, and add custom trace events to analyze. To use system trace, start profiling your app, click into the CPU Profiler, and then choose the System Trace recording configuration.
We now automatically save Profiler data as “sessions” to revisit and inspect later while you have Android Studio open. We’ve also added the ability to import and export your CPU recordings and heap dumps for later analysis or inspection with other tools.
Automatic CPU Recording
You can now automatically record CPU activity using the Debug API. After you deploy your app to a device, the profiler automatically starts recording CPU activity when your app calls startMethodTracing(String trace path) and stops recording when your app calls stopMethodTracing(). Similarly, you can also now automatically start recording CPU activity on app start-up by enabling Start Recording a Method Trace on Startup option in your run configuration.
JNI Reference Tracking
For those of you who have C/C++ code in your Android app, Android Studio 3.2 now allows you to inspect the memory allocations of your JNI code in the Memory Profiler. As long as you deploy your app to a device running Android 8.0 Oreo (API 26) and higher, you can drill down into the allocation call stack from your JNI reference. To use the feature, start a memory profiler session, and select the JNI Heap from the Live Allocation drop-down menu.
Android Studio 3.2 is a huge release with many exciting and welcome new features. On top of the user-facing additions, many stability and performance fixes are included under the hood.
What are your thoughts on Android Studio 3.2’s new features? Let us know in the comments.
Original Content published here: developer-tech.com