Android Studio 3.3: Fresh Look!

Android Studio 3.3- I’ve updated it already! Why haven’t you?

Google kicks off this new year with a stable release of Android Studio 3.3, with noteworthy enhancements and updates for developers who thrive for quality. There are no flashy new features but significant updates aiming to reduce the number of crashes, errors and memory leaks.

“Since the last stable release, Android Studio 3.3 addresses over 200 user- reported bugs.”

Android Studio 3.3 includes refinements in each of these sectors: development, build variants, testing and of course, optimization.

Android Studio’s “Navigation Editor” feature is now stable! The navigation editor basically comes up with a visual way to construct the navigation & transitions between various destinations inside an app. You can now specify the transitions among the screens using this visual tool. This navigation editor allows visualizing the entire application flow in a more comprehensive way as simple as drag-and-drop to link among the screens. To know more about how to use navigation drawer with navigation components, follow the instructions from this repo.

Navigation Editor in Android Studio 3.3

Ever got annoyed by the increasing file size when you try to build your past project with newer versions of Android Studio? Say no more! With Android Studio 3.3 and higher, a new dialog pops up to allow safe removal of the past installations of Android Studio. No, that’s not all! This release of Android Studio promises to help in cleaning unused cache directories and old configuration settings too!

It prompted me to delete the previous directories right away

One of the numerous headaches of the developers working and maintaining large Android application projects, includes build time and project sync time, especially if they have multiple build variants. After updating the IDE, navigate to Settings/Preferences > Experimental and under the section “Gradle”, check the box to enable active variant sync as the following suggests:

I enabled it manually by navigating to this path

I personally get excited whenever I find out any line of code, if added to gradle.properties, makes my developer life less time-consuming! Whether it’s a Gradle performance factor like Build Cache, Parallelize Build Optimization or Offline builds, I always keep my Gradle config updated to reduce project build times. On top of that, APK size has always been a significant factor and hence, we always use code shrinking solutions to get rid of unused code and resources and thus, making the APK file size smaller. On that note, a preview of Google’s new code shrinker, R8, has been included in this stable release. R8 detects and removes unused classes, fields, methods, and attributes from a packaged app, faster than ProGuard:

R8 does all of shrinking, desugaring and dexing in one step. When comparing to the current code shrinking solution, Proguard, R8 shrinks the code faster while improving the output size.

Just add this one line in your project’s gradle.properties & off you go:

android.enableR8=true

This version also includes 2 emojis in the bottom bar, used as sentiment buttons for those who share usage statistics to help improve Android Studio:

There are a number of minor updates, changes & added options in the optimization profilers too, naming Memory, Network & CPU Profilers to use these tools more conveniently. Head over to the Android Studio release notes andAndroid Gradle plugin release notes to give a quick read.

Thanks for reading! If you like what you just read and would like to recommend this, leave a 👏 !

Writes simple, stupid & hence, readable “okay” codes - mostly in Kotlin, Java, Python & Node. https://stackoverflow.com/u/11040422 https://github.com/SaadAAkash

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store