compose-ui

Follow these guidelines to create performant, reusable, and testable Composables. Make Composables stateless whenever possible by moving state to the caller. - Pattern : Function signature should usually look like: @Composable fun MyComponent ( value : String , // State flows down onValueChange : ( String ) -> Unit , // Events flow up modifier : Modifier = Modifier // Standard modifier parameter ) - Benefit : Decouples the UI from simple state storage, making it easier to preview and test. - ViewModel Integration : The screen-level Composable retrieves state from the ViewModel ( viewModel.uiState.collectAsStateWithLifecycle() ) and passes it down. - Default Parameter : Always provide a modifier: Modifier = Modifier as the first optional parameter. - Application : Apply this modifier to the root layout element of your Composable. - Ordering matters : padding().clickable() is different from clickable().padding() . Generally apply layout-affecting modifiers (like padding) after click listeners if you want the padding to be clickable.