The latest benchmark code uses Reanimated v3 apis itself for animations. The results are much similar to how it's been using the built-in Animated API. In fact what I found was Reanimated uses more memory than Animated api.

I also ran the benchmark for list view with new architecture enabled and also optimized and memoized the code (this is an unfair comparison since on flutter also i haven't done any explicit optimization). Surprising to see that it didn't make much different at all. will post all this in a separate article.

We do use reanimated library in our current app, but still we face janks in lower end to medium end devices in certain screens. The same screen performed smoothly in low end phones in flutter. Also when number of animated objects increases on the screen, flutter still retains relatively smooth experience while RN starts to struggle.

For example, one of our use case needs us to show confetti particles on screen. The most popular library react-native-confetti-cannon struggled a lot when we used higher number of practicles and the screen was very janky but flutter's confetti confetti library performed smoothly for the same number of particles without any visible jank.

I also tried the reanimated v3 implementation of confetti library react-native-reanimated-confetti , which also struggled a lot and the screen was frustratingly more janky for the same number of particles. Would be great if you can suggest a better confetti library if it exists.

Regarding expo library, many react native apps use CLI app instead of expo framework (Not to mention the higher application size that expo adds since its a wrapper around CLI)

Regarding the list test, in flutter list also the implementation is similar to how its done in React Native without rigorous optimization or extra memoization, so it's more like apples to apples comparison.

Having said that, I would love to update this benchmark post with more use cases and with flashlist also and see how it goes. Stay tuned :)