IssueTracker

Jetpack Compose version: 1.7.0-beta06 Jetpack Compose component used: AnimatedVisibility Android Studio Build: Android Studio Ladybug | 2024.1.3 Canary 3 | #AI-241.18034.62.2413.12138059, built on July 25, 2024 Kotlin version: 2.0.0

Here is the test simple:

    val isVisible = remember { mutableStateOf(false) }
    Column(
        modifier = modifier
    ) {
        AnimatedVisibility(isVisible.value) {
            Box(
                modifier = Modifier
                    .statusBarsPadding()
                    .size(300.dp, 100.dp)
                    .background(Color.Red)
            )
        }
    }

If you look at the stack trace you can see that AnimatedVisibility(false) does a lot of work. Most of the time androidx.compose.animation.core.TransitionKt.updateTransition and androidx.compose.animation.AnimatedVisibilityKt.AnimatedVisibilityImpl.

Why do I pay attention to this? Google documentation says that AnimatedVisibility is an analogue of if, but the behavior I see does not correspond to this at all.

With if(false) there will be nothing inside and it will not take time either. But with AnimatedVisibility(false) a huge amount of work is done, comparable to the fact that the animation is already running.

This seems broken to me. Please fix the behavior so that AnimatedVisibility(false) does not do the job and thus does not affect performance.