Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

NativeScript
NativeScript

326
479
+ 1
415
TypeScript
TypeScript

12.4K
9.5K
+ 1
407
Add tool

NativeScript vs TypeScript: What are the differences?

What is NativeScript? Build truly native apps with JavaScript. NativeScript enables developers to build native apps for iOS, Android and Windows Universal while sharing the application code across the platforms. When building the application UI, developers use our libraries, which abstract the differences between the native platforms.

What is TypeScript? A superset of JavaScript that compiles to clean JavaScript output. TypeScript is a language for application-scale JavaScript development. It's a typed superset of JavaScript that compiles to plain JavaScript.

NativeScript and TypeScript are primarily classified as "Cross-Platform Mobile Development" and "Templating Languages & Extensions" tools respectively.

"Access to the entire native api" is the primary reason why developers consider NativeScript over the competitors, whereas "More intuitive and type safe javascript" was stated as the key factor in picking TypeScript.

NativeScript and TypeScript are both open source tools. It seems that TypeScript with 51.1K GitHub stars and 7.06K forks on GitHub has more adoption than NativeScript with 17.2K GitHub stars and 1.27K GitHub forks.

According to the StackShare community, TypeScript has a broader approval, being mentioned in 982 company stacks & 1447 developers stacks; compared to NativeScript, which is listed in 9 company stacks and 26 developer stacks.

What is NativeScript?

NativeScript enables developers to build native apps for iOS, Android and Windows Universal while sharing the application code across the platforms. When building the application UI, developers use our libraries, which abstract the differences between the native platforms.

What is TypeScript?

TypeScript is a language for application-scale JavaScript development. It's a typed superset of JavaScript that compiles to plain JavaScript.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose NativeScript?
Why do developers choose TypeScript?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
      Be the first to leave a con
      What companies use NativeScript?
      What companies use TypeScript?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with NativeScript?
      What tools integrate with TypeScript?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to NativeScript and TypeScript?
      React Native
      React Native enables you to build world-class application experiences on native platforms using a consistent developer experience based on JavaScript and React. The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native.
      Ionic
      Free and open source, Ionic offers a library of mobile and desktop-optimized HTML, CSS and JS components for building highly interactive apps. Use with Angular, React, Vue, or plain JavaScript.
      Xamarin
      Xamarin’s Mono-based products enable .NET developers to use their existing code, libraries and tools (including Visual Studio*), as well as skills in .NET and the C# programming language, to create mobile applications for the industry’s most widely-used mobile devices, including Android-based smartphones and tablets, iPhone, iPad and iPod Touch.
      React
      Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.
      Flutter
      Flutter is a mobile app SDK to help developers and designers build modern mobile apps for iOS and Android.
      See all alternatives
      Decisions about NativeScript and TypeScript
      leonardo silveira
      leonardo silveira
      Software Engineer at Casa Magalhães · | 4 upvotes · 51.3K views
      NativeScript
      NativeScript
      Apache Cordova
      Apache Cordova
      Vue.js
      Vue.js

      So, i am preparing to adopt NativeScript.

      For years my hybrid projects used Apache Cordova.

      "Let's avoid to maintain two teams and double the deliver velocity".

      It was good for a few years, we had those september issues, (i.e. apple broke some backward compatibility) , but for the last years, things seems to be losing the grip faster.

      Last breaking changes, for instance, seems to have a workaround, however that growing feeling that simple things can not rely on so fragile webviews keeps growing faster and faster.

      I've tested nativescript not only on it's "helloworld", but also on how do they respond on issues.

      I got tweed support. I opened an github issue and got answers on less than 10 hours (yes i did it on another timezone and very close to a weekend). I saw the faulty docs get corrected in two days.

      The bad news is i only can adopt nativescript on newer projects, since there is no budget to revamp the current solutions.

      The good news is i can keep coding on Vue.js , without vou router, but that's ok. I've already exchanged vanilla html for real native app with background magic enabled, the router can be easily reproduced.

      See more
      Eli Hooten
      Eli Hooten
      CTO at Codecov · | 13 upvotes · 70.8K views
      atCodecovCodecov
      TypeScript
      TypeScript
      JavaScript
      JavaScript
      CoffeeScript
      CoffeeScript
      Vue.js
      Vue.js
      Visual Studio Code
      Visual Studio Code

      We chose TypeScript at Codecov when undergoing a recent rewrite of a legacy front end. Our previous front end was a mishmash of vanilla JavaScript and CoffeeScript , and was expanded upon haphazardly as the need arose. Without a unifying set of paradigms and patterns, the CoffeeScript and JavaScript setup was proving hard to maintain and expand upon by an engineering team. During a move to Vue.js , we decided to also make the move to TypeScript. Integrating TypeScript and Vue.js is fairly well understood at this point, so the setup wasn't all that difficult, and we felt that the benefits of incorporating TypeScript would outweigh the required time to set it up and get our engineering team up to speed.

      Choosing to add TypeScript has given us one more layer to rely on to help enforce code quality, good standards, and best practices within our engineering organization. One of the biggest benefits for us as an engineering team has been how well our IDEs and editors (e.g., Visual Studio Code ) integrate with and understand TypeScript . This allows developers to catch many more errors at development time instead of relying on run time. The end result is safer (from a type perspective) code and a more efficient coding experience that helps to catch and remove errors with less developer effort.

      See more
      Flow (JS)
      Flow (JS)
      Java
      Java
      React Native
      React Native
      TypeScript
      TypeScript

      I use TypeScript for Web Applications and for both frontend and backend because it has a lot of tooling around it and they really got the types and type safety right. Flow (JS) on the other hand lacks tooling and most of the times I scramble to find the right way of building my contracts in which TypeScript is very intuitive and natural. Additionally TypeScript is very similar to Java so your backend engineers and full stack engineers can work with it without much of context switch.

      The only time I think Flow shines is (based on probably my outdated knowledge) Flow is/was the only option if you want/wanted to build a React Native application mainly because React Native transpiler at the time I was working with it would only work with flow.

      See more
      TypeScript
      TypeScript
      Flow (JS)
      Flow (JS)

      I use TypeScript because it isn't just about validating the types I'm expecting to receive though that is a huge part of it too. Flow (JS) seems to be a type system only. TypeScript also allows you to use the latest features of JavaScript while also providing the type checking. To be fair to Flow (JS), I have not used it, but likely wouldn't have due to the additional features I get from TypeScript.

      See more
      David Koblas
      David Koblas
      VP Engineering at Payment Rails · | 9 upvotes · 14.9K views
      atPayment RailsPayment Rails
      JavaScript
      JavaScript
      Flow (JS)
      Flow (JS)
      TypeScript
      TypeSc