Then perhaps as @mzgreen suggests the Composables should just stack like a FrameLayout if we declare more than 1 for something like a Button. Then as a developer when I Preview the composable it’d render all strange and I’d be like “oh yeah, I need to define a Row/Column/ConstraintLayout to have them laid out properly”. Sensible defaults are fun until they’re different, e.g. if the sensible default for Button is to wrap the children in a Row, but the sensible default for Card is to wrap the children in a Column, then things might get confusing to the uninitiated as to why things magically work, but in different ways.