In a previous blog we described how API behavior changes advance the security and privacy protections of Android, and include user experience improvements that prevent apps from accidentally overusing resources like battery and memory.
The Bottom App Bar is an evolution of the traditional Top App Bar (a.k.a Toolbar or ActionBar in the Android world) which, one might argue, was the defining component of v1 of the Material Guidelines. The Bottom App Bar maintains the core features of an App Bar while offering a fresh look and functional improvements in key areas.
In May 2018, Google announced Android Jetpack / AndroidX — a collection of libraries which is meant to be the successor of the Support Library. Along with the AndroidX components, the tool named Jetifier was released. The goal of the Jetifier is to migrate your application’s dependencies and transitive dependencies to AndroidX preventing clashes between two different, but similar library groups. In other words, after running Jetifier during the build time, your project and your dependencies should be 100% migrated to AndroidX. In most cases, Jetifier is used during Gradle builds, though the standalone version is also available.
Last week I gave a talk at MobOS about writing and automating performance tests in Android. As part of the talk I wanted to demonstrate how you could detect memory leaks during your integration tests. To prove that I created an Activity using Kotlin that was supposed to leak memory but for some reason it didn’t. Was Kotlin helping me out without me knowing it?