Book Image

Getting Started with NativeScript

By : Nathanael J. Anderson
Book Image

Getting Started with NativeScript

By: Nathanael J. Anderson

Overview of this book

NativeScript allows you to build a fast cross-platform application that has a native UI. NativeScript is a true cross-platform framework that generates native speed applications using the native components of the host platform, all using JavaScript. Although NativeScript allows you to build your application in JavaScript, you have full access to the host OS from your code, allowing you to easily tweak or use new platform features instantly at native code speeds. Whether you have already developed multiple applications or zero applications, this book will help you to develop your next application in a cross-platform framework quickly, saving you a massive amount of time and money. This book concisely shows you NativeScript’s built-in framework that allows you to rapidly develop a fully-working compiled cross-platform application in just a few chapters. It starts by laying the foundation of NativeScript and working through the fundamentals to create a basic shell of the application. Moving on, you’ll see how to build a full-fledged application step by step. We’ll show you how to use plugins, and how to communicate with the native OS libraries easily so that you can customize your application as if your app was created in Java or Objective C. We then deal with the issues that arise from being cross platform and compensate for the different screen sizes, screen resolutions, and device abilities. Finally, we progress to testing and deploying your app.
Table of Contents (15 chapters)
Getting Started with NativeScript
About the Author
About the Reviewer

Unit testing on the device

During the final review of the book, the master branch (the totally unreleased versions) of the nativescript command introduced the brand new nativescript test command. Fortunately, I saw something appear in the repos and asked about it. Yours truly, living totally dangerously, pulled the absolute latest and greatest master versions of everything so that I can document the all new bleeding-edge way to do unit testing on devices and emulators.

The latest and greatest daily master runtimes are automatically built for all platforms on as a community service. So, in all reality, it was a simple download and install, and then I was running the latest and greatest bleeding-edge NativeScript code. Typically, the only reason you run from master is if you need a fix or some feature that isn't going to show up until the next major release, which might be a while from now.

Until now, we were trying to test our code outside of NativeScript. This is...