The keyboard covered the field, and the fix was not imePadding
Insets, soft-input mode, scroll position and focus order are four systems, and three are configured outside Compose.
ui
6 posts
An animation is state, and that is why it restarts
animate*AsState holds its value in the composition. A key change starts it over.
Streaming a response changes your UI contract, not just your latency
Partial output means every intermediate state is user-visible, including the wrong ones.
Constraints flow down, sizes flow up, and fillMaxSize means something specific
One measurement pass means a child cannot ask its parent how big it is.
A LazyColumn without keys loses your scroll position and your animations
Without a key, item identity is positional — so an insert at the top reuses every slot's state for the wrong item.
Modifier order is not style, it is semantics
padding then clickable gives a different touch target from clickable then padding — and both look identical.