NativeScript: Difference between revisions

Revision as of 06:52, 23 December 2016

Revision as of 08:45, 23 December 2016

Line 9:

| programming language = [[JavaScript]], [[TypeScript]]

| platform = [[Cross-platform]]

| license = [[Apache_LicenseApache License]]

| website = {{URL|www.nativescript.org}}

}}

'''NativeScript''' is an [[open-source software|open-source]] framework to develop apps on the [[iOS|Apple iOS]] and [[Android (operating system)|Android]] platforms. It was originally conceived and developed by Progress.<ref>https://www.infoq.com/news/2015/03/nativescript</ref>. NativeScript apps are built using platform agnostic programming languages such as [[JavaScript]] or [[TypeScript]]. NativeScript directly supports the [[AngularJS]] framework.<ref name=infoworld2893706>http://www.infoworld.com/article/2893706/mobile-development/javascript-native-ios-android-and-windows-phone-apps.html</ref>. Mobile applications built with NativeScript result in fully native Apps, which use the same APIs as if they were developed in [[Xcode]] or [[Android Studio]].<ref>http://searchcloudapplications.techtarget.com/podcast/NativeScript-framework-eases-cross-platform-app-development-woes</ref>. Additionally software developers can repurpose third-party libraries from Cocoapods, Android Arsenal, Maven and npm.js in their mobile applications without the need for wrappers.<ref>http://www.infoworld.com/article/3066900/javascript/nativescript-warms-up-to-angularjs-for-mobile-dev.html</ref> <ref>http://sdtimes.com/sd-times-github-project-of-the-week-nativescript/</ref> <ref name=visualstudiomagazine20150309>https://visualstudiomagazine.com/articles/2015/03/09/telerik-nativescript-beta-mobile.aspx</ref>.

==Development==

NativeScript was publicly released first in March 2015. Version 1.0.0 followed two months later.<ref>http://www.i-programmer.info/news/167-javascript/8561-nativescript-100-released.html</ref>. The framework quickly gained popularity reaching 3000 github-stars and over 1500 followers on twitter soon after the public release.<ref>https://www.nativescript.org/blog/nativescript-1.0.0-is-now-available</ref>. In the meantime, over 350 plugins are available, which are either officially supported by Telerik or stem from the open source community.<ref>http://nativescript.rocks/all.php</ref> <ref>https://www.npmjs.com/search?q=nativescript</ref>. The current version 2.4 supports [[iOS 10]] and contains support for [[AngularJS#Angular_2Angular 2|Angular]] 2.2.<ref>https://www.nativescript.org/blog/nativescript-2.4-announcement</ref> <ref>https://jaxenter.com/things-that-excite-me-about-angular-2-126528.html</ref>. The use of Angular is an optional development approach allowing for application source code to be shared between the web platform and mobile platform.<ref>http://www.cioreview.com/news/progress-releases-nativescript-20-with-crossplatform-deployment-capabilities-nid-14646-cid-19.html</ref> <ref>http://www.htmlgoodies.com/beyond/javascript/getting-to-know-angular-2.html</ref>.

==Structure==

NativeScript and the all required plugins are installed using the package manager [[Npm_Npm (software)|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.<ref name=heisede3282619>http://www.heise.de/developer/artikel/Mit-JavaScript-wie-hausgemacht-NativeScript-3282619.html</ref>. Telerik aims for a ratio of 90% common code between the iOS and Android platforms .<ref name="telerik.com">http://www.telerik.com/platform/nativescript/faq</ref>.

==Direct access to native platform APIs and Controls==

Platform independent user interfaces are defined using [[XML]] files.<ref>https://docs.nativescript.org/ui/basics</ref>. 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 <ref>https://github.com/NativeScript/NativeScript/blob/master/tns-core-modules/ui/button/button.ios.ts</ref> or com.android.widget.Button on Android .<ref>https://github.com/NativeScript/NativeScript/blob/master/tns-core-modules/ui/button/button.android.ts</ref>. 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 .<ref name=heisede3282619/>. Telerik aims for a ratio of 90% common code between the platforms <ref>http://www. name="telerik.com"/platform/nativescript/faq</ref>

While application source code is written in JavaScript, TypeScript or Angular, the source code is not compiled or otherwise mutated. The source code as is runs directly on the device. This architectural choice eliminates the need for cross-compiling or transpiling .<ref name=visualstudiomagazine20150309 />. Additionally, while the application source code is written in languages commonly encountered in a browser, or in a WebView contained mobile application, NativeScript applications run directly on the native device. There is no DOM manipulation or any mandatory browser interaction.<ref name=infoworld2893706/>.

==Notable features==

=== Native API Reflection (A.K.A 0-Day Access) ===

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.<ref name=infoworld2893706/>.

Another way the reflection feature is used is in working with 3rd party libraries. As JavaScript (or TypeScript/Angular) can talk directly to native code, there is no need to write binding layers in Objective-C, Swift or Java.<ref name=visualstudiomagazine20150309 /><ref>https://docs.nativescript.org/core-concepts/accessing-native-apis-with-javascript</ref> <ref name=visualstudiomagazine20150309 />.

Another way the reflection feature is used is in working with 3rd party libraries. As JavaScript (or TypeScript/Angular) can talk directly to native code, there is no need to write binding layers in Objective-C, Swift or Java <ref>https://docs.nativescript.org/core-concepts/accessing-native-apis-with-javascript</ref> <ref name=visualstudiomagazine20150309 />.

=== Angular 2 integration ===

With the launch of NativeScript 2.0, it is now possible to use Angular 2 to build cross-platform mobile applications <ref>https://www.nativescript.org/blog/nativescript-2.0---the-best-way-to-build-cross-platform-native-mobile-apps</ref>

Line 45:

*

*

==External links==

{{Portal|Free software}}