Google has released a stable version of Android Studio 3.5, as has Project Marble. This release addresses a number of issues, including fixing more than 600 bugs, 50 memory leaks, 20 IDE hangs, and improved XML&Kotlin type latency. In addition, for Android emulators, the impact of CPU and memory on the user’s development machine is reduced. No more worries about running out of AS memory!
Here are some notable features and improvements that come with this release:
One, the Layout Editor
Google has improved interactions ranging from constrained selection and deletion to better device preview resizing.
Second, the Data – Binding
The Google team looked into long-standing data binding issues. From a performance standpoint, it is found that creating data-binding expressions in XML files causes the code editor to seriously hang. After fixing this issue, code completion, navigation, and refactoring were improved.
In Android Studio 3.5, improved input latency makes it faster to edit data-binding expressions with XML.
Third, Build Speed
Another long-term problem with Android application development is the time it takes to build applications. The new version of Android Studio brings two significant improvements to application compilation. The first is the addition of incremental build support to the annotation processor, including Glide, AndroidX data binding, Dagger, Realm, and Kotlin(KAPT).
The second improvement involves disk I/O on Windows. Windows Defender(now called Windows Security) has the ability to scan files in real time (as they are created or modified) to protect users from malware. Android Studio 3.5 will display a hint on the steps you can take to exclude project directories from this real-time protection and complete the best Settings to speed up builds. Incremental support can have a significant impact on build speed. For example, in a preliminary analysis, just adding incremental support for Kotlin increased the change of non-ABI submodules in the Google I/O Schedule application from 9.1 seconds to 3.6 seconds — a 60% improvement.
Fourth, Apply Changes
The ability to quickly edit and view code changes without restarting the application is very efficient for application development. For example, if you change a line of Java code, you can Apply Changes and then Run. Two years ago, Google tried Instant Run to address this pain point, but it never worked as well as expected. A more practical approach, called Apply Changes, was rebuilt and implemented in Android Studio 3.5. Apply Changes uses Android Oreo and later platform-specific apis to ensure reliable and consistent behavior; Unlike the Instant Run mechanism, Apply Changes do not modify APK. To support these changes, the Google team redesigned the architecture of the entire deployment pipeline to improve deployment speed and tweaked the Run and Deployment toolbar buttons for a smoother experience.
This version has a new drop-down menu that allows you to quickly select which device to deploy your application to. This menu also includes a new option to run the application on more than one device at a time.
System health – Automatically recommends memory Settings
By default, Android Studio’s maximum memory heap size is 1.2GB. For many large projects, that may not be enough. Even if your machine has a lot of RAM, the IDE will not exceed this value. In Android Studio 3.5, the IDE recognizes when an application project needs more memory on a machine with higher memory capacity and notifies you in a notification to increase the memory heap size. Alternatively, you can make adjustments in the new Settings panel of Appearance & Behavior → Memory Settings.
System health -IDE speed
In the past, when we felt our IDE was slow, we turned off some Android Studio plugins, such as Android NDK support, to improve performance and make it more efficient for us to use. This time around, starting with Android Studio 3.5, the Google team removed some of the unnecessary performance memes that had previously affected the overall speed of the IDE.
System health-Lint code analysis
Lint code analysis, everyone is familiar with this, and companies can use this to scan for errors and useless files, as well as the possibility of null Pointers, very convenient. Android Lint is a code analysis framework in Android Studio that helps identify common programming errors. But some projects have C/C ++, which is pretty slow every time it’s analyzed. About 20-30 minutes. This seriously dampened my enthusiasm. After some digging, the Google team found and fixed several large memory leaks after Android Studio 3.5, resulting in approximately a 2x improvement in Lint performance. You can try it if you don’t believe me.
Sync recompile
There are red symbols in the application code, which is very painful. The solution is to re-run gradle Sync. The root cause of many red symbol events is that during recent Gradle changes, these caches were periodically removed to save disk space. Since Android Studio 3.5, the Google team has added conditional logic to check this state, and similar situations will be rare in the future.
Improvement of c++
C++ project support is also an area of focus in project Marble. For large projects, CMake builds are now 25% faster. In addition, an improved single build variable USER interface panel allows developers to specify ABI architectural goals individually. Finally, Android Studio 3.5 allows multiple versions of the Grale version of Android NDK to be used side by side in builds, which means multiple builds and alleviates incompatibilities between the NDK version and the Android Gradle plugin.
And so on there are a lot of people slowly in use to explore it, welcome to exchange ha.
Recommend:
1, big factory has a new open source project, hurry to get it…
2. The interviewer asked me: How many HTTP requests can a TCP connection send? I can’t answer that…
3, programmer suspected bug was hanged! High paying jobs in the Philippines?
4. After DeepNude was taken down, I found the technology involved on GitHub
5. What’s the path to native Android development
It’s amazing that someone can finally speak TCP/IP clearly
Tencent kaiyuan super practical UI wheel library, I am a wheel porter
8, Tencent’s new open source a bomb magic tool – zero reflection full dynamic Android plug-in framework officially open source
Like to pay attention to it, welcome to contribute!
