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
Credits
Foreword
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
13
Integration Testing with Appium

Android Keystores


On Android, you create your own application signing keys. As such, this key is used for the entire life of your application--by entire, I mean you use the same key to release every version of your application. This key is what links version 1.0 to v1.1 to v2.0. Without using the same key, the application will be considered a totally different application.

The reason there are two passwords is that your keystore can actually contain an unlimited number of keys, and so, each key in the keystore has its own password. Anyone who has access to this key can pretend to be you. This is helpful for building servers, but not so helpful if you lose them. You cannot change the key at a later time, so making backups of your keystore is extremely important. 

Note

Without your keystore, you will never be able to release a new version of the exact same application name, meaning that anyone using the older version will not see that you have an updated version. So, again, it is critical that...