ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
In Jetpack Compose, a remember block can trigger recomposition even when the values it captures have not changed, because the block’s invalidation logic does not correlate directly with observable parameter updates. As documented for Compose 1.6, this behavior persists, meaning UI trees may be rebuilt without explicit parameter changes, potentially impacting
Goal: Determine whether Jetpack Compose should automatically supply a MaterialTheme when Material components are used without an explicit provider, so teams can decide if relying on implicit theming is safe for production code. Uncertainty: The current implementation throws java.lang.IllegalStateException: No MaterialLocal found in Compose BOM 2023.10.00 and
I am working with Jetpack Compose 1.4 or later and need to understand whether the framework can infer stable keys for items in a LazyColumn or LazyRow when the underlying list is reordered or filtered. The documentation indicates that explicit keys are required to avoid unintended recompositions, but it is unclear whether any automatic key inference exists f
Stability System and Parameter Classification in Jetpack Compose Jetpack Compose's stability system determines whether a Composable can skip recomposition by analyzing parameter stability. Parameters marked as unstable always trigger recomposition of the parent Composable, even when the underlying data hasn't meaningfully changed. This becomes problematic in
Goal: Ensure that composables used in integration points such as AndroidView or ComposeView remain encapsulated within their defining module and are not unintentionally exposed as public APIs. Constraints: By default a @Composable function is public unless marked private or internal; lambdas supplied to AndroidView can capture and expose composables to the h
Integration boundary I am designing a screen where a legacy View hierarchy (containing its own touch handling, e.g. a custom map or drawing surface) is embedded in Jetpack Compose via AndroidView , and the surrounding Compose tree also uses pointerInput modifiers for gestures. Goal and constraints The goal is predictable, deterministic touch dispatch: I need
A LazyColumn backed by Paging 3 must supply a key lambda that preserves item identity across recompositions and configuration changes, especially when placeholders are enabled by default. Using the domain ID (key = it.id) works only if the ID is immutable; Paging 3 inserts null placeholders, forcing a null‑safe fallback such as it?.id ?: -position, and Remot
Memory Leak Risk from Lambda Captures in Jetpack Compose In Compose, a composable can capture references in lambda parameters. When the composable is removed from the composition tree, the runtime does not expose a public mechanism to nullify these references, raising the possibility that objects referenced by the lambda remain reachable and cause a memory l
The Jetpack Compose Navigation component relies on rememberSaveable to preserve UI state across configuration changes and process death. However, the scroll offset of a LazyColumn or LazyRow is not automatically saved by this mechanism, leaving the list reset to the top after a rotation or similar event. Developers who need the scroll position to survive nav
jetpackcompose