<@U045CL4PXRP> it’s a little hard to tell just fro...

# compose

[Richard Z]

@Toan Nguyen it’s a little hard to tell just from the info you showed, but one thing I notice is that there are stability-related issues. afaik, NavController is not considered “stable”, and therefore neither of the composable methods you screenshotted are skippable. Also, since the “non-stable” navController is captured in lambdas within those composables and therefore those lambda will be recreated on recomposition, almost no part of the composition is skippable. I’m hoping also ExampleModel is marked as @Immutable? This could help answer why DetailSportsScreen ends up recomposing multiple times when you don’t expect it to instead of being skipped. As for why it’s in the recomposition scope at all, I think you’d have to look further up into your navigation layer.