>The fact that these vendor-supported toolkits – SwiftUI and Compose – are built atop the platform-native scrolling mechanics I can't speak for iOS, but neithe

>The fact that these vendor-supported toolkits – SwiftUI and Compose – are built atop the platform-native scrolling mechanics I can't speak for iOS, but neither RecyclerView nor Compose's scrolling is built on top of the Android platform's scrolling - they both implemented new and different ways to do scrolling versus the ScrollView or ListView the platform shipped with. Both were built using the same public APIs any developer could use. The reason they offer the performance they do is implementation choices by the developers who wrote them, around what work to perform when. Lots of Android developers implemented scrolling using the platform APIs and got jank, others implemented scrolling before RecyclerView was even available and had smooth performance. There is no magic performance guarantee because you transpile to kotlin.