Recalculated, not recomposed: what does one tap cost in a Compose paywall?
RevenueCat engineers trace a ~0.4-second lag after tapping a plan on an Android paywall, starting from a user screen recording. The article breaks down the cost of override resolution in a server-driven Compose UI, derivedStateOf dependency tracking, regex caching, font equals, work moved to the draw phase, and an invisible spinner, plus instrumented tests and kill switches for measuring a single tap.
What this means for indie developers：Developers building Compose paywalls or server-driven UIs can borrow its method for measuring single-interaction jank and its derivedStateOf pitfalls.