Book Image

NativeScript for Angular Mobile Development

By : Nathan Walker, Nathanael J. Anderson
Book Image

NativeScript for Angular Mobile Development

By: Nathan Walker, Nathanael J. Anderson

Overview of this book

NativeScript is an open source framework that is built by Progress in order to build truly native mobile apps with TypeScript, JavaScript or just Angular which is an open source framework built by Google that offers declarative templates, dependency injection, and fully featured modules to build rich applications. Angular’s versatile view handling architecture allows your views to be rendered as highly performant UI components native to iOS and Android mobile platforms. This decoupling of the view rendering layer in Angular combined with the power of native APIs with NativeScript have together created the powerful and exciting technology stack of NativeScript for Angular. This book focuses on the key concepts that you will need to know to build a NativeScript for Angular mobile app for iOS and Android. We’ll build a fun multitrack recording studio app, touching on powerful key concepts from both technologies that you may need to know when you start building an app of your own. The structure of the book takes the reader from a void to a deployed app on both the App Store and Google Play, serving as a reference guide and valuable tips/tricks handbook. By the end of this book, you’ll know majority of key concepts needed to build a successful NativeScript for Angular app.
Table of Contents (24 chapters)
Title Page
About the Authors
About the Reviewer
Customer Feedback
Integration Testing with Appium


Throughout, we have been working hard creating a solid foundation to build our app on. We created a CoreModule to provide some low-level services, such as logging, and a persistent store and designed the module to easily scale in more services as needed . Plus, this module is portable and can be dropped into other projects with your own company's special sauce intact.

In typical app development, you may want to run your app on the iOS and/or Android simulator along the way, during this process to double-check some of your design/architecture choices and that would be advisable! We just haven't done that yet, since we have an app pre-planned here and want you to stay focused on the choices we are making and why.

We also created the two primary feature modules that our app needs for its core competency, PlayerModule and RecorderModule. The player will be pre-setup with 2-3 recorded tracks loaded and ready to play right upon launch, so we will be bootstrapping our app with the PlayerModule...