3 ms·
We haven't tried in months so I can't give a scientific answer but our assessment early on was more that due to the diversity of Android devices. The low end on
by Vishnevskiy 10y ago
We haven't tried in months so I can't give a scientific answer but our assessment early on was more that due to the diversity of Android devices. The low end ones that are for sale even now won't perform well enough for our use case.
- davidpelaez 10y agoDid your case have some things that make it heavy in some way? e.g. very long list with many images, data structures that were big and kept in memory? Video or heavy animations? Or not really and the whole thing was just slow?
- Vishnevskiy 10y agoWe ran the exact same code (minus the Chat view) that we have on iOS which performs really well. It performed poorly on Android devices we care about. Touch events would lag (because of the JS computations hey resulted in), animations would be choppy (Android has native Animated.js now though, we haven't tried it). Our conclusion was since we already had a pretty good native Android app it was probably not investing time in a degraded experience. We will maybe try again in the future but the gut feeling is JS performance on many slow cores (Android devices love this) is obviously not as good as two fast cores (iOS devices).
- lacker 10y agoThe performance of the native Animated class is much better than handling animations in JS - definitely give that a try if you're trying RN again. I'm curious about touch events - what JS computations were happening on touch events, was it complex and app-specific or was it something relatively standard?