Note: This documentation is adapted from the sublime NativeScript Vue docs, so first of all, a big thank you to the NativeScript Vue community for their hard work providing the foundation for this documentation. Contributors are credited in the source.
React is an industry-standard library for developing user interfaces.
What is React NativeScript?
React NativeScript is a React custom renderer that allows you to describe a NativeScript app using the familiar React 'way of thinking'.
Why would you use this (and not React Native)?
In brief: React NativeScript puts native access at the front of the developer experience.
This architecture makes native access a chore – any native access from the JS context is necessarily asynchronous, and a lot of boilerplate is needed to set up a JSON-compatible communication interface between the two contexts. Any alterations to native code also require a recompile of the app.
NativeScript (and therefore React NativeScript), by comparison, runs its JS VM on the main thread, and is bridgeless, with JS-native bindings to all the platform's APIs. This means that we can access native functionality synchronously simply by calling it via JS. Native development becomes even faster thanks to JS facilitating hot reload.
How is its compatibility with the React ecosystem?
React NativeScript can use anything that isn't coupled to a particular React renderer. So, for example, Redux will work (as it is simply a state store), but React Navigation (which depends upon React DOM or React Native) won't.
React NativeScript cannot consume code from React Native projects – that's a whole large-scale separate project. Support for non-UI plugins from the React Native ecosystem is a long-term area of interest, however.
Want to get involved?
React NativeScript is an open-source project and contributions are very much encouraged. Join us on the
#react channel on the NativeScript Community Slack to chat.
Who supports it?
Nobody; it's purely been a labour of love. A donation page may pop up at some point in the future, however.
Is it production-ready?
It is feature-equivalent with NativeScript Core, which itself is production-ready (as is React); the question is how well that implementation has been achieved. Until users start picking it up and identifying holes in it, we can't be sure.