For example, we took a look at the app deployment flow to a device, and completely re-architectured and replaced Instant Run with Apply Changes so that it’s more reliable and trusted. On top of memory and performance, we spent time polishing and fixing core user facing feature areas. ![]() Project Mable was a focused period to work on the IDE and Android Emulator system health but it also uncovered a set of quality areas we will continue to work on going forward. Additionally, for the Android Emulator, we decreased the CPU and memory impact on your development machine. Then, the team addressed a range of issues from fixing over 600 bugs, 50 memory leaks, 20 IDE hangs, and improving XML & Kotlin typing latency. We did this to establish a safety net to catch issues that are typically difficult to catch with regular unit testing. To improve system health in Android Studio, we first created a new set of infrastructure and internal dashboards to better detect performance problems. ![]() Working on Project Marble was in direct response to feedback from you and we continue to welcome any further feedback you have. We called this initiative Project Marble, and it focused on making the fundamental features and flows of Android Studio & Emulator rock-solid by looking at three core areas: system health, feature polish, and bugs. This stable version of Android Studio is a different kind of release where the Android Studio team took a step back from large feature work for eight months and instead focused on product quality to further accelerate your day-to-day app development. Have you ever wished that Android Studio was faster, more performant, and more memory efficient? If so, then download Android Studio 3.5 today. Posted by Jamal Eason, Product Manager, Android
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |