Common shared element use cases

When animating shared elements, there are some particular use cases that have specific recommendations.

Asynchronous images

It's common to use a library to load up an image asynchronously, such as when using Coil's AsyncImage composable. For it to work seamlessly between two composables, its recommended to set the placeholderMemoryCacheKey() and memoryCacheKey() to the same key as a string derived from the shared element key, such that the cache key is the same for the matched shared elements. The new shared element will be using its match's cache as the placeholder until it loads the new image.

The typical usage for AsyncImage is as follows:

    model = ImageRequest.Builder(LocalContext.current)
        .placeholderMemoryCacheKey("image-key") //  same key as shared element key
        .memoryCacheKey("image-key") // same key as shared element key
    placeholder = null,
    contentDescription = null,
    modifier = Modifier
                key = "image-key"
            animatedVisibilityScope = this


To animate fontSize changes, use Modifier.sharedBounds(), resizeMode = ScaleToBounds(). This transition makes the size change relatively fluid. The contentScale parameter can be tweaked to animate a specific font weight or style.

    text = "This is an example of how to share text",
    modifier = Modifier
                key = "shared Text"
            animatedVisibilityScope = this,
            enter = fadeIn(),
            exit = fadeOut(),
            resizeMode = SharedTransitionScope.ResizeMode.ScaleToBounds()

TextAlign changes are not animated by default. Instead use Modifier.wrapContentSize() / Modifier.wrapContentWidth() over using different TextAlign for shared transitions.