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

Chapter 10. @ngrx/store + @ngrx/effects for State Management

Managing state in any app can become troubling as the app scales over time. We want to have full confidence over the predictability of our app's behavior and getting a hang of its state is key to gaining that confidence.

State can be broadly defined as the particular condition that someone or something is in at a specific time. With regard to our app, the state can encompass whether our player is playing or not, whether the recorder is recording or not, and whether the track list UI is in mixing mode or not.

Storing state in a single spot allows you to know exactly what the state of the app is at any given moment. Without a single store, you usually wind up with state buried throughout different components and services, which often leads to two or more different versions of state as features are built out. This unwieldy growth of state becomes even more troublesome as different features need to interact with each other, which may...