What users are saying about
18 Ratings
92 Ratings
18 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 5 out of 100
92 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8.8 out of 100

Attribute Ratings

  • React is rated higher in 2 areas: Likelihood to Recommend, Support Rating

Likelihood to Recommend

5.0

NativeScript

50%
13 Ratings
8.2

React

82%
12 Ratings

Likelihood to Renew

8.0

NativeScript

80%
1 Rating

React

N/A
0 Ratings

Usability

NativeScript

N/A
0 Ratings
9.0

React

90%
2 Ratings

Support Rating

1.0

NativeScript

10%
3 Ratings
10.0

React

100%
6 Ratings

Likelihood to Recommend

Progress Software Corporation

I gotta be honest, after a PoC period, we choose to rewrite the whole application in a different cross-platform app. Our developers had to invest a lot of time and effort to debug a lot of plugin-related issues, which we needed to utilize the android mobile phone capabilities. QR reader, special visualizations, and fine-tuning were really hard and often resulted in writing native Android code instead of using the shared Angular code. In the end, we think that writing a standalone Android app and an Angular app would have been a better alternative, as the shared code base was so unreliable that it did not save us any time.
Read full review

Open Source

React is great for people who are trying to build complex single page web applications. It is intuitive for developers, encourages modularity through components, and provides a web app this will scale. React may not be suited as well for simple websites or static content. However, this is changing with frameworks like Gatsby which allow you to build static HTML websites using React.
Read full review

Pros

Progress Software Corporation

  • True native app. The app uses native components and that is quite noticeable in the overall performance of the app. NativeScript is also awesome in the way we can access the native APIs, so we are never really constrained by the framework. If we need, we can just dive into the native APIs without leaving our environment and language (JS).
  • Cross-platform. Builds for Android and iOS. It deals with the platforms differences very well.
  • Support for Vue.js. Even though it is just a community effort, the NativeScript-Vue plugin is the best alternative to build native Apps with Vue.js. That was a major factor to go with NativeScript.
Read full review

Open Source

  • React is designed around the notion of generated html as opposed to templated html. This provides more flexibility in building elements on a page, and allows developers to create html that is programmatically configured based on runtime considerations.
  • React uses JSX, which is HTML templating integrated into javascript code. This simplifies the generation of complex structures, especially those that vary based on runtime and interactive data.
  • React is more efficient because it generates a virtual DOM rather than directly building in in the actual DOM. By building 'offline' in this manner, the DOM generation is faster. After building, it can be installed in one operation.
  • React only builds those portions of the display that have changed, making display updates more efficient.
Read full review

Cons

Progress Software Corporation

  • The need to know the native Android and iOS APIs to access device hardware and other platform-specific functionality
  • Not all user interface components are available for free
  • NativeScript has no HTML and DOM, which requires some deep knowledge of different UI tools to be implemented instead
Read full review

Open Source

  • React could get very frustrating unless you start thinking in React. React enforces a top down hierarchy of data flow and offers no way for the data to communicate backwards. This is a big shift in mindset coming from Angular 1.x. This constraint is really a big factor that determines how to organize your code and how you might want to write your own Components.
  • Because of the self imposed top down hierarchy, you end up having a heavy parents with dumb children. Because parents would need to the bulk of the work, they usually manage the state, while passing callbacks to the child components. If not properly designed, this could lead to the callback hell, where you could have callbacks passing through like multiple children.
  • As with any library, you will have to iterate through multiple designs to come up with a ways to avoid "heavy parent components" in React. One obvious solution is using some open source tools like Redux, but we opted for a variation of it to suit our needs.
Read full review

Pricing Details

NativeScript

Starting Price

$0

Editions & Modules

NativeScript editions and modules pricing
EditionModules

Footnotes

    Offerings

    Free Trial
    Free/Freemium Version
    Premium Consulting/Integration Services

    Entry-level set up fee?

    No setup fee

    Additional Details

    The NativeScript framework and CLI are completely free and open source. NativeScript Sidekick is a free download to improve developer productivity with optional paid tiers for power users.

    React

    Starting Price

    Editions & Modules

    React editions and modules pricing
    EditionModules

    Footnotes

      Offerings

      Free Trial
      Free/Freemium Version
      Premium Consulting/Integration Services

      Entry-level set up fee?

      No setup fee

      Additional Details

      Likelihood to Renew

      Progress Software Corporation

      The hybrid is ok but native is better for performance and the right use case I want to go for is the performance without dealing with too many development tools.
      Read full review

      Open Source

      No answers on this topic

      Usability

      Progress Software Corporation

      No answers on this topic

      Open Source

      React is just a bit of a different animal. I was avoiding it for the longest time. I thought for sure I would land on Vue or something else with a more approachable and familiar appearance. But after taking an online course in React, I started realize what people were raving about (and complaining about) and decided to implement it at our office for one of our products.
      Read full review

      Support Rating

      Progress Software Corporation

      The community support is excellent.
      They have a slack community as well as a discourse forum
      forum.nativescript.org
      Both of these offer community driven support.
      The forum is more for a threaded discussion. The slack community is more for a quick talk.
      Read full review

      Open Source

      Since it's open-source and very popular, the community support for React and related tools and libraries is excellent. There are a lot of people using the same tools, and so issues tend to get fixed quickly and "recipes" are easy to come by. And since it's backed by Facebook, they have a dedicated engineering team working on the progression of React.
      Read full review

      Alternatives Considered

      Progress Software Corporation

      Ionic Ionic is an excellent Angular-based framework for mobile, and it does give a lot of access to the native device api's. However, the technology is based on Cordova, which means the apps being built are just webviews, with html, css and JS all running on the UI thread, and potentially creating very slow experiences for users. NativeScript is a truly native solution, and so provides a faster user experience. ReactNative We evaluate ReactNative, and found it much the same as NativeScript. The main difference is that your JS is all written with React, while NativeScript lets you choose between normal JS, Angular, and Vue. For our team, Angular was the most appropriate choice.
      Read full review

      Open Source

      I have also used Angular before coming to React. Web apps created with React are much faster than Angular because React is based on virtual DOM which reloads only those components of the web page that change and everything else remains the same. Angular's learning curve is also slightly steeper than React.
      Read full review

      Return on Investment

      Progress Software Corporation

      • The poor quality of NativeScript documentation has the potential to weigh heavily on development timelines, budgets, and QA resources in a NEGATIVE manner.
      • The poor interoperability of NativeScript plugins can significantly increase development time.
      • The need to seek out professional instruction to learn how to use NativeScript effectively may become a burden on your budget.
      • The number of breaking changes between versions of NativeScript, may cause your development efforts to lag further behind the most recent releases of NativeScript and your other chosen environments than you are accustomed to.
      • NativeScript still does not support the latest major version of Angular. Any significant changes to the other environment components of your systems may hold you back even further while NativeScript plays catch-up.
      Read full review

      Open Source

      • React allows a modular design, which is fabulous for A/B testing (showing a different module to each user). Some of these experiments had an improvement as big as to pay for the whole team that coded it. So far we know the ROI has been positive, but I can't provide a number.
      Read full review

      Screenshots

      Add comparison