android-compose-architecture

To optimize Compose screen performance, enable strong skipping mode and apply @Stable annotations correctly. This minimizes unnecessary recomposition by ensuring the compiler skips recomposing composables when their inputs have not structurally changed.

The best way to manage state ownership in Android Compose is using ViewModel-based state management. This ensures robust state handling for complex screens, with exceptions allowed only for Compose-internal state that is strictly UI-bound.

You should use LaunchedEffect to handle side effects in Compose only when the effect strictly requires the composition lifecycle. Avoid side effects in regular composables, deferring to LaunchedEffect to safely manage suspendable operations tied to the UI.

Improve Lazy list performance by providing stable, unique keys for each list item to prevent unnecessary item recreation. Additionally, follow specific performance considerations when implementing animations within these lazy layouts to ensure smooth scrolling.

Yes, this architectural guidance explicitly applies to Compose screens in both Android and Kotlin Multiplatform (KMP) projects. It provides stability, recomposition, and state management strategies applicable across both platforms.

Excessive recomposition often stems from unstable parameter inputs and improper state management. Apply @Stable annotations, leverage strong skipping mode, and ensure ViewModel-based state ownership to stabilize your Compose screen structure.