Gain insights into building reactive websites with RxJS. Delve into mastering observables and managing events efficiently to create fast, responsive applications while reducing bugs.

c.tar.gz

stopWatch2

codewidgetJobDetach

dcrx

stopWatch2-tmux

codewidgetJobDetach-copy

rx-photos-ng

Angular

rx-photos-ng-initial

rx-angular-pizza

rx-angular-perf

rx-angular-bad-perf

rx-angular-good-perf

rx-angular-pizza-copy

stopWatch2-tmux-serv2

fightergame

The list of requirements for frontend work keeps increasing. Websites that load quickly on shaky connections, render perfectly on mobile devices, and respond with lightning speed to user input are expected. All of these tasks require dealing with a high number of events from disparate sources, be it your Customer Relationship Management (CRM), late-breaking news, or just a chat room.

Observables is a new way of thinking about managing these events, even when they may occur sometime in the future.

In this course, you’ll learn how to delegate both the calls and control flow to RxJS, allowing you to focus on the rest of your application.

RxJS compartmentalizes eventing flows, encapsulating each action in a single function, providing many helper operators that keep an internal state, allowing you to outsource your state worries to the library.

By the end of this course, you will be able to build bigger, faster, and less-buggy applications for your users.

Build Reactive Websites with RxJS: Master Observables and Wrangle


# Routing analytics
Let's hook up some analytics trackers to Angular's router.  Instead of listening in on individual routes, this service needs to know about every route change.  Generate a new service and attach it to the routing module with `ng g service analytics`.



>  <span style="font-size: 1.5em">⚠️</span> 
>  While working locally, make sure you're on the latest version of the Angular CLI.  Older versions will fail, with `"Error: Specified module does not exist."`


Open the fresh `analytics.service.ts` and modify it to add in some structure for recording routing changes:





# Routing analytics
Let's hook up some analytics trackers to Angular's router.  Instead of listening in on individual routes, this service needs to know about every route change.  Generate a new service and attach it to the routing module with `ng g service analytics`.



>  <span>⚠️</span> 
>  While working locally, make sure you're on the latest version of the Angular CLI.  Older versions will fail, with `"Error: Specified module does not exist."`


Open the fresh `analytics.service.ts` and modify it to add in some structure for recording routing changes:




 Let's add some analytics to track how people use the site and plugin a universal HTTP error handler.

Course Introduction

Creating Observables

Manipulating Streams

Managing Asynchronous Events

Advanced Async

Multiplexing Observables

Using HTTP in Angular

Building Reactive Forms in Angular

Advanced Angular

Reactive Game Development

Adding in Analytics

Routing analytics