NativeScript

NativeScript is an open-source framework to develop apps on the Apple iOS and Android platforms. It was originally conceived and developed by Progress.[2] NativeScript apps are built using platform-agnostic programming languages such as JavaScript or TypeScript. NativeScript directly supports the Angular framework [3] and supports the Vue framework via a community-developed plugin [4]. 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.[5] Additionally, software developers can re-purpose third-party libraries from Cocoapods, Android Arsenal, Maven, and npm.js in their mobile applications without the need for wrappers.[6][7][8]

Development

NativeScript was publicly released first in March 2015. Version 1.0.0 followed two months later.[9] The framework quickly gained popularity reaching 3000 github-stars and over 1500 followers on twitter soon after the public release.[10] In the meantime, over 600 plugins are available, which are either officially supported by Progress or stem from the open source community.[11][12] The use of Angular is an optional development approach allowing for application source code to be shared between the web platform and mobile platform.[13][14]

Structure

NativeScript and all the required plugins are installed using the package manager npm. Projects are created, configured, and compiled via the command line or a GUI tool called NativeScript Sidekick [15]. Platform-independent user interfaces are defined using XML files. NativeScript then uses the abstractions described in the XML files to call native UI elements of each platform. Application logic developed in Angular 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.[16] Progress aims for a ratio of 90% common code between the iOS and Android platforms.[17]

Direct Access to Native Platform APIs and Controls

Platform-independent user interfaces are defined using XML files.[18] 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 target operating system. This means a call to the NativeScript Button API provides a UI abstraction for Button, which directly calls UIButton on iOS [19] or com.android.widget.Button on Android.[20]

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.[8] 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.[3]

Notable Features

Native API Reflection (a.k.a. 0-Day Access)

Another notable feature is the use of reflection to handle native API endpoints. 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.[3]

Another way the reflection feature is used is in working with third 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, Java or Kotlin.[8][21]

Angular Integration

With the launch of NativeScript 2.0, it is possible to use Angular to build cross-platform mobile applications [22].

Vue Integration

The Vue framework is supported in NativeScript thanks to a community-driven effort to develop a plugin [4].

References

  1. ^ https://www.nativescript.org/faq
  2. ^ https://www.infoq.com/news/2015/03/nativescript
  3. ^ a b c http://www.infoworld.com/article/2893706/mobile-development/javascript-native-ios-android-and-windows-phone-apps.html
  4. ^ a b "{N}-Vue". nativescript-vue.org. Retrieved 2017-10-31. 
  5. ^ http://searchcloudapplications.techtarget.com/podcast/NativeScript-framework-eases-cross-platform-app-development-woes
  6. ^ http://www.infoworld.com/article/3066900/javascript/nativescript-warms-up-to-angularjs-for-mobile-dev.html
  7. ^ http://sdtimes.com/sd-times-github-project-of-the-week-nativescript/
  8. ^ a b c https://visualstudiomagazine.com/articles/2015/03/09/telerik-nativescript-beta-mobile.aspx
  9. ^ http://www.i-programmer.info/news/167-javascript/8561-nativescript-100-released.html
  10. ^ https://www.nativescript.org/blog/nativescript-1.0.0-is-now-available
  11. ^ http://nativescript.rocks/all.php
  12. ^ https://www.npmjs.com/search?q=nativescript
  13. ^ http://www.cioreview.com/news/progress-releases-nativescript-20-with-crossplatform-deployment-capabilities-nid-14646-cid-19.html
  14. ^ http://www.htmlgoodies.com/beyond/javascript/getting-to-know-angular-2.html
  15. ^ "NativeScript Sidekick - your faithful companion for app development". NativeScript.org. Retrieved 2017-10-31. 
  16. ^ http://www.heise.de/developer/artikel/Mit-JavaScript-wie-hausgemacht-NativeScript-3282619.html
  17. ^ http://www.telerik.com/platform/nativescript/faq
  18. ^ https://docs.nativescript.org/ui/basics
  19. ^ https://github.com/NativeScript/NativeScript/blob/master/tns-core-modules/ui/button/button.ios.ts
  20. ^ https://github.com/NativeScript/NativeScript/blob/master/tns-core-modules/ui/button/button.android.ts
  21. ^ https://docs.nativescript.org/core-concepts/accessing-native-apis-with-javascript
  22. ^ https://www.nativescript.org/blog/nativescript-2.0---the-best-way-to-build-cross-platform-native-mobile-apps

External links