View profile Newsletter - Issue #120 Newsletter - Issue #120
By Mark Murphy, CommonsWare • Issue #120 • View online
This week, we spend time trying to understand compositions: when do things enter, when do things leave, and how can figure out why they are recomposed?
In addition, we ease our way through some animations, understand why our composables are slow in development, and go another couple of rounds on the “what to use for navigation?” cycle. We examine a PIN/OTP widget and how to render a dashed line. And, now that we have Maps Compose, I wonder where the rest of the Google Play composables are.

One Off the Stack, One Off the Slack
You’ve got questions. That’s understandable!
How Can a Composable React to an Image?
Composable Commentary
Posts, videos, and other new information related to Jetpack Compose!
Medium: Easing in to Easing Curves in Jetpack Compose
Medium: Why should you always test Compose performance in release?
Podcast: ADB on Live Edit
Medium: Implementing a fully-custom Design Language System with Jetpack Compose — Part 2/2: Components
Video: What Does Recomposition Mean to Your App?
Medium: The State of Navigation in Jetpack Compose
Podcast: Learning Jetpack Compose with Vinay Gaba
Medium: Collapsible App Bar With MotionLayout in Jetpack Compose
Medium: How To Accomplish Dynamic Absolute Positioning In Android’s Jetpack Compose
Resource Roundup
100% pure code!
…And One More Thing
We are nearing the one-year anniversary of the first stable release of Compose. I had expected that once Compose was stable that Google would put a lot of pressure on developers to use Compose UI, akin to how Google started pressuring developers to use Kotlin. In particular, I had expected that other Google teams would start offering composables, or at least composable wrappers. That has not happened nearly to the level that I anticipated.
IOW, where are all the Google Play composable SDKs?
Maps Compose is a fine example of what I was expecting. It offers a Google-supplied first-class composable API for embedding Google Maps. While you can use AndroidView to wrap a MapView, having a solution developed and maintained by the Maps developers helps ensure that we are doing a good job in using Maps in Compose.
But, where are the rest?
Google Cast, AdMob, Google Identity, and others all have UI elements that could benefit from a supported composable wrapper. None seem to have one, though perhaps I am just not finding them (which would be its own problem).
Perhaps Google focused on Maps because of the sheer complexity of the Maps API. That is fine, but some of the others have their own challenges. For example, Google Cast places an emphasis on an ActionProvider for use in an action bar, and it is unclear how that can be used in a Compose environment.
With luck, these teams will start offering first-class Compose support in the coming months. If another year goes by and we are still asking “where are all the Google SDKs?”, that would seem to be a bad sign.
Did you enjoy this issue?
Mark Murphy, CommonsWare

Jetpack Compose news and notes.

In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue