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?
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
to wrap a
, 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 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.