Google has announced Android Studio 3.3, focusing on the quality and finesse of its new features. More specifically, it was officially announced that Android Studio 3.3 comes with a navigation editor, full support for applications, system upgrades, improved debugging and improved Java compilation while using annotation editors. In addition, the profiler options are more detailed and low frame highlighting has been added to help the user remove bugs faster. Below is more detailed information about the new features that we will see.
#1 Navigation editor
In Android Studio 3.3, the navigation editor allows you to create destinations, specify parameters, and define the transition between them. This is a big improvement, as the user will be able to see the entire path of the application. If you use the navigation architecture, you can connect each action via drag-and-drop.
#2 Profiler tracking options
The profiler allows you to choose the level of data collection for live memory allocation on devices running API 26 or above. Also with Android Studio 3.3 you can choose between full or sample mode. This can improve the performance of your application while profiling and helps you get one step closer to the real-life user experience. Also, the CPU profiler allows you to see how much each frame takes to give to the UI thread.
#3 Instant apps
You can now create an instant app and an installed app in the same project. This makes it easier to separate your app and scale it. To deploy your app as an instant app, edit the current refactoring and enable the option.
#4 Better information for debugging when using deprecated APIs
If your app uses obsolete APIs, Android Studio provides you with more information about how to debug the required part of the code. To enable this option, add the following line of code to a Gradle file: “android.debug.obsoleteApi = true”
#5 Improved Java Compilation
Android Studio 3.3 allows you to get better Java compilation, as long as you use annotation editors.
#6 Improvements to the build system, providing R8 code shrinker and refactoring the lazy task
Finally, regarding the R8 code shrinker, it is much faster than ProGuard and does not require many code changes. Also, the Android Grandle plugin now uses a lazy task refactoring of the API, which avoids the cost of creating new tasks during the Grandle configuration phase.
