ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Conflict detection and automatic restart Jetpack Compose's snapshot system uses optimistic concurrency: when Snapshot.apply() detects that another snapshot has committed changes to the same State record since the current snapshot was opened, it throws SnapshotApplyConflictException and discards the pending writes. The recomposition machinery catches this exc
I have a multi-module Android project using Jetpack Compose (compiler 1.5.x, Kotlin 1.9). UI state is modeled as plain Kotlin data classes in a shared :core:model module, and composables in :feature modules consume them. The generated Compose compiler reports show these data classes classified as unstable , even though they contain only val properties of pri
Goal Determine whether Jetpack Compose should expose a runtime budget API or compile-time guard for rememberSaveable to prevent TransactionTooLargeException when saved state surpasses the platform's IPC parcel limit. Constraints and uncertainty The Activity savedInstanceState Bundle enforces a ~50–100 KB parcel budget that varies by Android version and OEM.
Goal: implement a retry‑on‑failure coroutine that updates a mutableStateOf value exactly once per successful attempt while guaranteeing that no state access occurs after the composable disposes. Constraints/uncertainty: The retry loop must survive transient failures but must not leak coroutines that continue after disposal, which triggers the IllegalStateExc
When a ComposeView embedded in an XML layout hosts an AndroidView that itself renders a Compose subtree via a nested ComposeView, the two composition boundaries each require a ViewCompositionStrategy. The outer ComposeView typically uses DisposeOnViewTreeLifecycleDestroyed to survive configuration changes, while the inner ComposeView may need DisposeOnDetach
Goal Determine whether invoking ComposeView.setContent from a non-UI thread is the direct cause of intermittent IllegalStateException failures, and whether the exception reflects a hard composition concurrency limit rather than a transient lifecycle race. Constraints The exact exception string may change between Compose runtime releases, so message matching
When an Android app is restored from Auto Backup, Compose UI state held by rememberSaveable is not recovered. The SavedStateRegistry that backs rememberSaveable is excluded from the backup payload, so any counter, scroll position, or form input stored this way resets to its initial value after reinstall. Persistent storage such as DataStore or SharedPreferen
Goal Determine whether derivedStateOf can skip recalculation when multiple coroutines mutate the same source state between composition frames in Jetpack Compose. Constraints and uncertainty derivedStateOf tracks state reads during its calculation block and recomputes only when a tracked state object changes. Under concurrent writes, Compose may skip intermed
Static Compiler Metrics Versus Runtime Recomposition Counts The goal is to decide which signal to trust when optimizing a Jetpack Compose recomposition bottleneck: the build-time Compose compiler report or the runtime recomposition count from Layout Inspector. The compiler plugin classifies composables as skippable or non-skippable based on stability inferen
jetpackcompose