Blog

NativeScript modules are JavaScript modules that adhere to the CommonJS specification and provide access to native APIs through the NativeScript runtime. Because NativeScript modules adhere to CommonJS, npm is a perfect place to store them.

Saving user settings a device’s local storage is a common requirement for mobile applications. Because of that, we made the creation of a settings page with NativeScript straightforward. In this blog post you’ll learn how to build a settings page using the latest bits of NativeScript—XML declaration, data-binding, and CSS styling.

We know how important it is for a new framework to have samples, so you will be able to find several good examples of open source applications built with NativeScript in our Github organization. Open http://github.com/nativescript and search for repositories named after the following pattern "sample-SAMPLE_NAME". All the samples are licensed under the BSD license.

This is the first article from a series of articles we are planning to release as we progress with the application implementation. The full source code of the application is here: http://github.com/nativescript/sample-Tasks.

With NativeScript you can use your JavaScript and CSS skills to write native mobile applications for iOS, Android and very soon WindowsPhone. There is no WebView involved in rendering the app, as the UI is rendered by the native platform's rendering engine. Because of that the, app's entire UX is native.

NativeScript is a runtime that lets you build native iOS, Android, and (soon) Windows Universal apps using JavaScript code. NativeScript has a lot of cool features, such as two-way data binding between JavaScript objects and native UI components, and a CSS implementation for native apps. But my favorite feature, and the subject of this article, is NativeScript’s mechanism for giving you direct access to native platform APIs.