|Original author(s)||Telerik by Progress.|
|Developer(s)||Telerik and community|
2.5 / February 1, 2017
NativeScript was publicly released first in March 2015. Version 1.0.0 followed two months later. The framework quickly gained popularity reaching 3000 github-stars and over 1500 followers on twitter soon after the public release. In the meantime, over 450 plugins are available, which are either officially supported by Telerik or stem from the open source community. The current version, 2.5, contains support for Webpack 2.0, Chrome Developer Tools and many enhancements to improve the developer experience. The use of Angular is an optional development approach allowing for application source code to be shared between the web platform and mobile platform.
NativeScript and all the required plugins are installed using the package manager npm. Projects are created, configured and compiled via the command line. Platform independent user interfaces are defined using XML files. NativeScript then uses the abstractions described in the XML files to call native elements of each platform. Application logic developed in Angular2 and TypeScript can be developed independent of the target platform as well. A NativeScript mobile application is built using the node.js runtime and tooling. Telerik aims for a ratio of 90% common code between the iOS and Android platforms.
Platform independent user interfaces are defined using XML files. NativeScript uses the XML data structures representing the cross platform abstraction to trigger platform specific code that directly interacts with the native elements of the deploy target operating system. This means a call to a NativeScript provides UI abstraction for Button, will directly call UIButton on iOS  or com.android.widget.Button on Android. Application logic developed in Angular2 and TypeScript can be developed independent of the target platform as well. A NativeScript app is build using the node.js runtime and tooling. Telerik aims for a ratio of 90% common code between the platforms 
Another notable feature is the use of reflection to handle native API end points. Rather than require separate binding layers between NativeScript and each mobile platform API, NativeScript uses reflection to gain information and metadata about the native platform APIs. New features added to any native platform API are available immediately.
With the launch of NativeScript 2.0, it is now possible to use Angular 2 to build cross-platform mobile applications 
Manage research, learning and skills at defaultLogic. Create an account using LinkedIn or facebook to manage and organize your IT knowledge. defaultLogic works like a shopping cart for information -- helping you to save, discuss and share.