Reading Jesse’s article started me thinking about one of my favourite problems in the Android world: Navigation. Navigation is a key part of any application that has more than two screens. Which is probably most of them. But navigation on Android sucks.
In August, we announced plans to expand Android Auto’s app ecosystem to enable new navigation, parking, and electric vehicle charging apps. We’ve been hard at work collaborating with our early access partners to test and refine the Android for Cars App Library.
The Android Studio 4.1 release introduces a Database inspector, Dagger navigation support, a native memory profiler, improvements for Apply Changes, the ability to use the emulator directly inside Android Studio, and more!
A registry that stores activity result callbacks for registered calls. You can create your own instance for testing by overriding onLaunch(int, ActivityResultContract, I, ActivityOptionsCompat) and calling dispatchResult(int, O) immediately within it, thus skipping the actual Activity.startActivityForResult(Intent, int) call.