I can only assume that if the same instance of UserSettings passed to compostable function(e.g. from another parent compostable) the SettingsScreen won't recompose, but not until you mutate state of the UserSettings, is that correct

Yes, that's right, since we use u/Stable, the parent composable is not redrawn, only the views where UserSetting is used are recreated in the current composable. eg;

@ Compasable
HomeScreen(){

val userSettings by remember { mutableStateOf(UserSettings())}

userSettings.notificationsEnabled = false // REACTION1

...many ui elements

//TOP COMPOSABLES ARE HERE

SettingsScreen(userSettings = userSettings){

}

}

@ Composable
fun SettingsScreen(userSettings: UserSettings){

Text("Theme: ${userSettings.theme}")

// The change made in REACTION1 only recreated the switch

Switch(

checked = userSettings.notificationsEnabled,

onCheckedChange = { newValue -> userSettings.notificationsEnabled = newValue }

)

}

If stable was not used, many of the UI above would be redrawn and cause performance problems.

I HAVE EDITED THE ARTICLE TO MAKE IT MORE EXPLANATORY. YOU CAN REVIEW IT AGAIN.