> If you are constantly passing large amounts of data between the JS thread and the Native thread or constantly changing the layout (which passes data between t

> If you are constantly passing large amounts of data between the JS thread and the Native thread or constantly changing the layout (which passes data between the threads) you are doing it wrong. I’m working on an alternative to React Native that does exactly this, and it works absolutely fine: React NativeScript. In NativeScript (and thus also React NativeScript), the JS logic and the UI both execute on the UI thread. Furthermore, you can synchronously access any native API without needing to set up bridging code; bindings to the whole Obj-C/Java runtimes are ready-generated. https://github.com/shirakaba/react-nativescript https://github.com/shirakaba/react-nativescript https://react-nativescript.netlify.com/ https://react-nativescript.netlify.com/