Describe state hoisting and its benefits in Compose
WHAT IT TESTS: Understanding unidirectional data flow in declarative UI. ANSWER OUTLINE: Move state to the caller, pass value and event lambda down, keep them stateless. RED FLAG: Internal state in reusable composables or calling hoisting boilerplate.
WHAT IT TESTS: Whether you understand unidirectional data flow and can separate UI rendering from state ownership in Compose. ANSWER OUTLINE: Define hoisting as moving state to the caller and exposing value and onEvent lambdas. Explain benefits: stateless composables are reusable across screens, preview-friendly, and testable without mocks. Note the caller owns the single source of truth. RED FLAG: Arguing that rememberSaveable in a low-level composable is fine, or treating hoisting as unnecessary boilerplate.
Read the original → developer.android.com
- #android
- #jetpack-compose
- #state-hoisting
- #ui-architecture
- #declarative-ui
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.