Google Releases Android Studio 3.6

Posted on February 24, 2020 by Paul Thurrott in Dev, Android with 2 Comments

Android Studio 3.6 focuses on core code editing and debugging quality is the first update since Google’s Project Marble, which helped shore up IDE quality.

“We learned a lot from Project Marble, and in Android Studio 3.6 we introduce a small set of features, polished existing features, and spent a notable effort addressing bugs and improving underlying performance to ensure we meet the high quality bar we set in the past year,” Google’s Scott Swarthout writes in the announcement.

Some of the key improvements in Android Studio 3.6 include:

Multi-display support. The Android emulator now includes preliminary support for multiple virtual displays.

New split view in the design editors. Now, you can quickly design, develop and preview app layouts using XML.

Embedded Google Maps. Now, you no longer need to manually type in GPS coordinates to test location-aware apps.

Automatic memory leak detection for Fragments and Activities. Now, you can automatically optimize your app and find bugs with automatic memory leak detection for Fragments and Activities.

There’s a lot more, so check out the original post for the details. As always, you can download Android Studio from the Android Developer website.

Tagged with

Join the discussion!

BECOME A THURROTT MEMBER:

Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Register
Comments (2)

2 responses to “Google Releases Android Studio 3.6”

  1. imranpk

    Real nice information

  2. bill_russell

    The main reason for memory leaks is because of the side effects of Android's rotation handling mechanism, of recreating the activites and fragments, etc, traditionally not a fun thing to deal with, even though seeming easy on the surface.

    A major point of Java is auto memory management, automatically preventing memory leaks or using programming patterns that would be impractical with manual memory management. I always immediately force to portrait mode, solving that. Then again I only do prototype apps, but most apps other than games and video apps should not rotate, period.