sambiopic

I'm Director of Developer Relations and a Google Developer Expert for Angular and Web Technologies. I believe anyone who wants to learn to code should be able to learn code and I love teaching. When I'm not coding or writing, you'll find me outside hiking or camping in the beautiful Pacific Northwest.

Director of Developer Relations

Sam Julien

Auth0’s Sam Julien and Kim Maida spoke at ng-conf 2019 in Salt Lake City.

The State of Angular: ng-conf 2019

eHk3ciM

I am the Group Manager, Developer Content at Okta, and a Google Developer Expert in Web Technologies and Angular. I'm passionate about identity, authentication, constant learning, and developer communities. As a developer advocate, engineer, mentor, and international speaker, I love learning from and sharing with other inhabitants of the tech space.

Group Manager, Developer Content

Kim Maida

Angular v4, realtime, rendering on the server, best practices, and more. Read about the sessions from ng-conf 2017 (April 7) Day 3.

ng-conf 2017 Summary - Day 3

Angular v4 has been released. Read about Fair Day from ng-conf 2017 (April 6) Day 2.



**TL;DR:** Learn about the "open-track" Fair Day at [ng-conf 2017](https://www.ng-conf.org/) on April 6, 2017 (Day 2 of 3).

---

## ng-conf 2017: Fair Day

Day 2 of ng-conf 2017 was Fair Day. There were workshops and sessions running simultaneously with other activities and entertainment such as combat bots, board games, VR park, Prison Escape Bus, Experts Rooms, and lounge/hack rooms. In addition to general fair activities, I attended sessions on ngrx, Apollo and GraphQL, machine learning with Angular, and improving components. You can check out summaries of these sessions below.

---

## ngrx

[Ngrx](https://github.com/ngrx) consists of small, concise libraries built with RxJS to solve problems such as state management and side effect management in Angular.

### ngrx/store

Ngrx/store is an [RxJS state management container](https://auth0.com/blog/managing-state-in-angular-with-ngrx-store/) heavily based on Redux. It uses actions, reducers, and a single store. A reducer is a function of state. The initial state goes in, then handles each action and returns the new state. Reducers are pure functions. ngrx/store abstracts away the application reducer so that child reducers only handle one piece of the state. New reducers can be added to manage their own individual slices of state.

The `dispatch()` and `select()` methods are used to send actions to the reducer to update state, and return an observable of only changed state, respectively. We may want to write concise components and refactor `select()` out to _selectors_. This way, we can share the selectors across the application. Selectors should be stored where our state is defined. Abstracting the selectors puts less responsibility on the component to know how to get the selected data.

### ngrx/effects

Any code that interacts with the outside world is a [side effect](https://auth0.com/blog/glossary-of-modern-javascript-concepts/#purity). We don't know how they're going to behave when that code is run. For example, API calls are side effects. Isolating side effects out of the component tree makes them easier to test.

Ngrx/effects is a side effect model. With it, we can listen for certain actions, perform side effects, and deliver new actions back to the store. The `@Effect()` decorator hints to tell the store to subscribe and returns an observable of an action. This can be mapped to its payload. When implementing ngrx/effects to manage side effects, we've performed the same action but the component has a lot less responsibility. Components are now a pure representation of state.

### ngrx Performance Improvements

Reducers are pure, so we don't need Angular to perform any deep dirty checking. Angular only needs to check if the reference has changed.

### Redux Devtools Extension

We can also wire up the Redux Devtools Chrome extension in our ngrx application. Importing `StoreDevtoolsModule` provides a bridge to the Chrome extension, and we can then instrument store in the `app` module. Doing so incurs a performance penalty, so it's important to only use in development. The Redux Devtools extension provides an interface to see what the state of the application looks like, complete with a time traveling debugger.

> _"Redux is not great for making simple things quickly. It's great for making complex things simple."_ —Brandon Roberts & Mike Ryan

---

## Managing Data with GraphQL

Angular has solved developer issues and concerns with initial loading and size, prerendering, rendering, transitions, and animations. These are no longer concerns.

However, we are still left with a concern regarding network latency. Users expect instant feedback, ie., when liking something on Facebook. Caching and prefetching can reduce network latency. When looking for a library that handles network and data management problems, [Apollo](http://dev.apollodata.com/angular2/) offers solutions along with its dev tools.

Improving network performance is not an all-or-nothing solution. Think about data and the network when creating your apps. Every effort makes your app a little bit faster, so anything you do helps. Here are two things we can address:

* Send fewer requests.
* Send less data in the requests.

When using REST APIs, particularly those we have little control over, we call the server and can frequently get a _lot_ of information back. This can be a mess, but we can use [GraphQL](http://graphql.org/) to describe what info we want and get just this information at the field level.

With GraphQL and Apollo:

* It doesn't matter how many resources we query, we'll get everything in one single response in the structure desired.
* We can create an Apollo query with the exact structure we want back and it returns an observable.
* We can take advantage of code autocompletion with the data that could come back from the server; this creates a good separation of concerns regarding the front end and back end.
* We can also change data with post and put requests (mutation).

By using queries inside components, we create a "super Redux or ngrx" that understands the larger picture and brings back only what we need from the server. Within components, we can query only for what is needed for that particular component.

We do _not_ need a GraphQL backend in order to take advantage of GraphQL on the client. We can achieve the benefits without touching the server at all, _or_ we can build middleware that can query any data sources.

Check out [urigo's repos on GitHub for examples](http://github.com/urigo).

---

## Build, Measure, and Machine Learn with Angular

### Build Measure Learn

**Conversion** refers to crafting solutions that lead to users doing what you want them to do. For example, this might be downloading an ebook, subscribing to your service, signing up for a newsletter, etc.

We build features and then we want to measure the features and see if visitors like the features or not. We then learn about the visitors and using this information, build better features in the next cycle to increase conversion.

The most important part of any data analysis is how the data captured. [Redux Beacon](https://github.com/rangle/redux-beacon) is an open source library created at [Rangle](http://rangle.io). Redux Beacon wiretaps Redux sections in an app and sends them to a target of your choice for conversion and reporting purposes, allowing you to map Redux or ngrx actions and state to your analytics data model.

### A/B Testing

When just gathering data is not enough, A/B testing can also be performed with [feature toggles](https://github.com/rangle/feature-toggle-ng2-redux). Almost anything on your website that affects visitor behavior can be A/B tested. This includes features, colors, buttons, CTAs, headlines, etc. The problem with A/B testing is that we learn the more successful option, but we don't know the user demographic that caused this result, and analysts want to know this information.

Regionally, visitors might pick different options. For example, if  a visitor is close to your office geographically, they might choose an "In Office Training" call to action whereas people located far away may only select "Online Training".

### Machine Learning

A custom Redux Beacon target sends raw data set for each user showing the pages they visited, their location, and more. This data can be passed to a machine learning algorithm that can use patterns to generate a model. This can then show scores with a probability of given user behaviors. This is called a **decision tree model**. Machine learning can predit the probability of which decision a user will make based on the user's behavior.

In a nutshell, the steps to do this are:

* Save the data.
* Convert that data to vectors.
* Train the predictive model.
* Generate the rules.
* Do the predictions.

---

## Using Directives

Mike Brocchi talked about utilizing directives in Angular. When building out an application, we build out a component tree, but where do we go from there? If we want to reuse logic, we factor it out into a service. What happens if we have behavior in the component that we want to be able to use elsewhere? The answer is directives, which are underused in the current version of Angular.

There are three types of directives:

* Attribute-based, ie. `[ngClass]`
* Structural, ie. `*ngFor`, `*ngIf`
* Components

Mike focused on attribute-based directives. With directives, we can add behaviors just by adding an attribute to an existing element. We can then pass values in using `@Input()` and use host binding to access DOM properties and manipulate them. We can also use host listeners to handle events, such as clicks. After applying a directive, we can expose events by emitting them to the parent component with event emitters and outputs.

Directives provide a way to share both logic and behavior throughout an application _without_ the burden of unneeded templates. They are underused in the current version of Angular, but can provide powerful shared functionality.

---

## Aside: Auth0 for Angular

It's a great time to explore Angular for your single page JavaScript applications. Auth0 can help out by providing authentication, a JWT library, Quick Start documentation, and tutorials. Check out some of the following resources:

* [JWT library for Angular](https://github.com/auth0/angular2-jwt)
* [Angular 2+ Quick Start with Auth0](https://auth0.com/docs/quickstart/spa/angular2)
* [Migrating an AngularJS App to Angular eBook](https://auth0.com/e-books/migrating-to-angular2)
* [Managing State in Angular with ngrx/store](https://auth0.com/blog/managing-state-in-angular-with-ngrx-store/)
* [Angular 2 Authentication Tutorial](https://auth0.com/blog/angular-2-authentication/)

You can <a href="https://auth0.com/signup" data-amp-replace="CLIENT_ID" data-amp-addparams="anonId=CLIENT_ID(cid-scope-cookie-fallback-name)">sign up for a free Auth0 account here</a>!

> Auth0 provides the simplest and easiest to use [user interface tools to help administrators manage user identities](https://auth0.com/user-management) including password resets, creating and provisioning, blocking and deleting users. [A generous **free tier**](https://auth0.com/pricing) is offered so you can get started with modern authentication.

---

## Conclusion

Day 2 of ng-conf 2017 was packed with workshops, networking, and fun activities. Day 3 will be normal single track sessions.

You can tune into the [ng-conf 2017 livestream here](https://www.ng-conf.org/livestream) as well as watch recorded streams from previous days.


ng-conf 2017 Summary - Day 2 (Fair Day)

Angular v4 has been released. Read the major takeaways from ng-conf 2017 (April 5) Day 1.

ng-conf 2017 Summary - Day 1

99c4080f412ccf46b9b564db7f482907?s=200 avatar

99c4080f412ccf46b9b564db7f482907?s=200

I'm currently a Senior Developer Advocate at MongoDB. I'm also a Google Developer Expert for Web Technologies and spend most my time giving talks at conferences and meetups, mentoring developers and running workshops, and creating online content to help technology professionals.

Former Auth0 Employee

Ado Kukic

The final day of ng-conf focused on reactive programming, Firebase and much more. Check out our summary of ng-conf day three. 



Day three of ng-conf consisted of a single track of talks. The topics covered today included reactive programming, Firebase, Angular 2 form validation and animations amongst others. The question on everyones mind at the end of day three was **"When will Angular 2 be released?"** and we still don't have a definite date. One thing we do know for sure is that the Angular 2 offline compiler is one of the key missing pieces, so as soon as it lands, we'll know the release is imminent.

<include src="TweetQuote" quoteText="One of the key missing pieces to the final release of Angular 2.0 is the offline compiler."/>

If you missed our previous recaps of ng-conf, you can check out the big announcements from [day one](https://auth0.com/blog/2016/05/05/ng-conf-summary-day-1/) and [day two](https://auth0.com/blog/2016/05/06/ng-conf-summary-day-2/).

## Reactive Programming

Angular 2 has fully embraced [reactive programming](https://en.wikipedia.org/wiki/Reactive_programming) patterns. The [**ngrx**](https://github.com/ngrx) GitHub group has already released a number of libraries that enable Angular 2 components to implement reactive functionality. These include the [ngrx/store](https://github.com/ngrx/store), [ngrx/router](https://github.com/ngrx/router), [ngrx/db](https://github.com/ngrx/db) and [ngrx/devtools](https://github.com/ngrx/devtools), with more libraries to come.

## AngularFire 2 Enters Beta

If you've worked with Angular and Firebase, there's a good probability you've interfaced with the [AngularFire](https://www.firebase.com/docs/web/libraries/angular/) library. [AngularFire 2](https://github.com/angular/angularfire2) provides an easy to use API for interfacing with Firebase with your Angular 2 applications. Firebase is a real-time database that allows automatic syncing across all connected devices. It was announced that as of today, AngularFire 2 is available to download and use in a public beta state.

## Angular 2 Form Validation

We took a deep-dive into the different ways to create and validate forms and user input with Angular 2. Developers can choose to implement forms via a **template driven** or **model driven** architecture. Template driven allows the developer to define the form in the actual view layer, while model driven forms are defined programmatically and generated by Angular 2 itself.

## Codelyzer

Codelyzer will save Angular 2 developers a ton of time when building applications. Codelyzer examines the developer defined rules and requirements that are set up via JS or TS lint files as well as the Angular 2 style guide, and when the standards are not adhered to, Codelyzer will complain and let the developer know of the rules they are violating. Codelyzer is also built into the Angular CLI and can be used starting today.

## Animations

There are many ways to handle animations on the web. You can do pure CSS animations, JavaScript animations or a mix of the two. The Angular team is aiming at making animations simpler but more powerful with Angular 2. Within Angular 2 components, developers will be able to define and implement different types of animations. This abstraction will allow for a greater increase over control as well as performance, which will be a great benefit, as traditionally animations on the web have been difficult to implement properly.

## Angular CLI

Angular CLI solves the problem of diving into Angular 2 app development. Where in the past, you would have a lot of manual configuration and setup, with the CLI, scaffolding and starting an application can be done in as little as three terminal commands:

```bash
ng new PROJECT_NAME
cd PROJECT_NAME
ng serve
```

The Angular CLI will simplify many tasks including: project scaffolding, creating of new services and components, running linting and other tasks as well as handling build and deploy of Angular 2 applications. You can get started with the Angular CLI by running the `npm install -g angular-cli` command from a terminal window. *NodeJS and npm are required.*

## Conclusion

The conference may have ended but the Angular 2 journey has just begun. With the release candidate out in the wild, developers can finally start developing Angular 2 applications with a certain level of confidence that the API will not change drastically before the final 2.0 release. Brad Green, the managing director of the Angular project, has stated in the Q&A panel that he believes that Angular 2 is production ready and references several use cases where Angular 2 is already used in production including Google AdWords, Capital One and the Weather Channel.

Now is the right time to jump into Angular 2 development. If you are already developing an Angular 2 app or are just getting started, chances are you will need an authentication system and Auth0 has you covered. Check out our [Angular 2 JWT](https://github.com/auth0/angular2-jwt) helper library that works with both Auth0 and any other implementation of JSON Web Token (JWT) authentication. To quickly get started, <a href="https://auth0.com/signup" data-amp-replace="CLIENT_ID" data-amp-addparams="anonId=CLIENT_ID(cid-scope-cookie-fallback-name)">sign up</a> for a free Auth0 account and get user authentication setup with your Angular 2 app in minutes.

ng-conf 2016 Summary - Day Three

Day two of ng-conf 2016 was Fair Day. We got to deep dive and learn more about what's in the pipeline for Angular 2.



Day two of ng-conf was titled **Fair Day**. Fair day consisted of a brief keynote in the morning and then a series of breakout sessions and workshops allowing developers to deep dive into all the new technologies announced on day one. Check out our [recap of day one](https://auth0.com/blog/2016/05/05/ng-conf-summary-day-1/) to learn about these technologies which include Angular Universal, Material, CLI, Augury and Mobile Toolkit. Day 1 was all about big announcements, [day three](https://auth0.com/blog/2016/05/07/ng-conf-summary-day-3) went hands-on on how to work with Angular 2 and associated projects.

## The Future of Angular 2

It may be a bit early to discuss the future of Angular 2 when it's not even out yet officially, but a key theme of today's keynote was the future of Angular 2. Angular offline compiling, advanced Material Design components and effortless upgrades for the future were discussed.

<include src="TweetQuote" quoteText="It's early to discuss the future of Angular 2, but the theme of the day 2 keynote was looking ahead."/>

### Offline Compiler

Offline compiling is what allows the Angular 2 library to become smaller than Angular 1. This is done through a custom compiler that the Angular team built, which is invoked through the `ngc` command once installed, which examines your apps code and does tree shaking to remove any unnecessary modules. The ng-compiler is one of the key features of Angular 2 that is required before Angular 2.0 can be delivered but as of today it is not ready.

### Advanced Material Components
The Material Design team gave a brief talk about the future of Material Design with Angular 2. The team has already committed to parity with the existing Material 1 for Angular 1.x, but talked about future potential with components that could include components such as `<md-map>` which would embed a Google Map or `<md-chart>` which would be used for charting UI. The coolest potential component discussed was `<md-text-editor>` which would create a WYSIWYG text-editor which have traditionally been difficult to implement, especially with Angular 1 applications.

### Seamless Upgrades

Finally, the team discussed effortless future upgrades and even joked about Angular 3. The goal here is to give developers a seamless path to upgrading once future 2.x versions of Angular are released. The Angular team is already doing extensive testing to ensure that any change to the core Angular libraries does not break compatibility with existing modules. 
 
## Angular 2 Workshops
  
There were plenty of Angular 2 workshops that took a deep dive into some of the technologies announced on day one of the keynote. Ionic had a great presentation on building hybrid mobile apps with Ionic 2 and Angular 2. The Telerik team took to the stage again and gave a detailed walkthrough of how to build native mobile applications with Angular 2 and NativeScript. Sean Larkin did a great workshop on integrating Angular 2 with Webpack.
 
 Auth0 hosted a workshop on integrating JSON Web Token (JWT) authentication with both Angular 1.x and Angular 2. The workshop highlighted the benefits of JWT authentication as well as differences in implementation between the two frameworks. If you would like to learn how to implement JWT authentication in your app check our guide for both [Angular 1](https://auth0.com/docs/client-platforms/angularjs) and [Angular 2](https://auth0.com/docs/client-platforms/angular2). If you don't already have an Auth0 account, <a href="https://auth0.com/signup" data-amp-replace="CLIENT_ID" data-amp-addparams="anonId=CLIENT_ID(cid-scope-cookie-fallback-name)">sign up</a> for free and get started today.
 
## Conclusion - Day 3 Preview
 
 Tomorrow is the final day of ng-conf 2016. TypeScript, Animations, React Native and AngularFire are just some of the talks in store. We can't wait to learn more about Angular 2 and will be sure to give a detailed summary of day three. You can follow the live stream tomorrow on the ng-conf official [website](https://www.ng-conf.org/). 

ng-conf 2016 Summary - Day Two

Angular 2 has reached the release candidate milestone. Learn more and get caught up on all the news coming out of ng-conf 2016.



The annual [ng-conf](https://www.ng-conf.org/) conference is upon us once again. This year, Angular 2 is all the rage. Angular 2 has entered [release candidate](https://github.com/angular/angular/blob/master/CHANGELOG.md#200-rc0-2016-05-02) and is inching ever-closer to a final 1.0...err...2.0 release.

In today's short post, we'll recap all the big announcements coming out of ng-conf 2016. Be sure to check out the big announcements from [day two](https://auth0.com/blog/2016/05/06/ng-conf-summary-day-2/) and [day three](https://auth0.com/blog/2016/05/07/ng-conf-summary-day-3/) as well.

## Keynote

[Brad Green](https://twitter.com/bradlygreen) opened up ng-conf this year with some pretty impressive announcements. Over 360,000 developers are already using Angular 2 in some capacity. Angular 2 is five times faster than Angular 1 and is already smaller than Angular 1 by almost 20kb which will help reduce load times of Angular 2 developed apps. Brad also announced a variety of Angular products that will truly make Angular 2 a leading platform for developing web and mobile applications. We'll examine these in depth below.

<include src="TweetQuote" quoteText="Angular 1 is a framework. Angular 2 is a platform. - Brad Green"/>

### Angular Universal

![Angular Universal](https://images.ctfassets.net/23aumh6u8s0i/3Q44br69UZgGdoceGb1p30/3b2e347f95541162f7f517d0c5f88cce/universal)

[Angular Universal](https://universal.angular.io) will allow developers to run their Angular 2 applications directly on the server. With Angular 1, the applications always ran on the client side, which made things like search engine optimization (SEO) and social sharing links difficult to implement as web crawlers generally do not execute JavaScript before scraping a webpage. When a user would share an Angular 1 app to Twitter for example, rather than seeing the title and description of the post they would instead see angular bindings `{title}` and `{description}` unless the developer spent extra time implementing a prerenderer.

Angular Universal currently works with [NodeJS](https://nodejs.org/en/) and [ASP.NET](http://www.asp.net/), with more frameworks and languages supported in the future. Applications are built just as they would be on the front end with some slight changes to accompany features that servers do not have available such as setting up a redis store instead of localstorage. Angular Universal apps are rendered on the server and then sent to the client. This greatly decreases load times on mobile devices and makes the apps feel snappier.

### Angular CLI

![Angular CLI](https://images.ctfassets.net/23aumh6u8s0i/edtMqHyhZZ8DYqivUaXWJ/6a2e3a72714fc29a45ad2c3f5ee1b610/cli)

[Angular CLI](https://cli.angular.io) aims to simply the way developers build Angular 2 apps. Where in the past you'd have to do a lot of the manual configuration to get up and running, with Angular CLI, you can type simple commands in your terminal such as `ng generate component` and the CLI will scaffold a new component for you.

The Angular CLI will do more than just scaffold new components and services for you though. It will help with both the build and deploy stages as well as linting, testing and formatting your applications.

### Angular Mobile Toolkit

![Angular Mobile](https://images.ctfassets.net/23aumh6u8s0i/6U5bPSOpT0ZtDxbrNAXPCL/3ecc8851990c99d35189ddbdcbb0a6ee/mobile)

[Angular Mobile Toolkit](https://mobile.angular.io) will allow developers to build progressive mobile apps with Angular 2. Progressive mobile apps are an evolution of mobile apps built with HTML, CSS and JavaScript with a few key features: **instant loading**, **offline support**, **installable** and **handle notifications**.
 
 The debate between building native vs progressive mobile is heavily debated and both have their pros and cons. Native apps have **better performance**, **re-engagement** and **access to hardware APIs**. Web apps on the other hand have **searchability**, **shareability** and **less friction/wider marketshare** going for them.
 
 The good news with Angular 2, you can build both native mobile apps, which we'll get to in a bit, as well as progressive mobile apps.
 
 <include src="TweetQuote" quoteText="Angular 2 allows developers to build both native and progressive mobile apps."/>
 
### Material 2

![Angular Material](https://images.ctfassets.net/23aumh6u8s0i/1QpphjaXgdm9wjNgVkD3A6/d9c7f8959a29ff2583eca55a8666ef89/material)
 
The de-facto design language for Android is [Material Design](https://www.google.com/design/spec/material-design/introduction.html), which is slowly making it's way to the web. Angular 1 already has a great library which implements a variety of Material Design patterns and Angular 2 is getting the same treatment. [Material 2](https://material.angular.io/) is in an early alpha state at present but already has a variety of components implemented including checkboxes, form input elements, buttons and more.
 
Material 2 will allow developers to quickly build beautiful user interfaces without having to write a lot of custom CSS. The Material 2 team has also announced that they are working on a "Component Toolkit" which will implement best practices for building user interfaces with Angular 2 that will be decoupled from Material Design itself.
 
### Augury for Angular 2

![Angular Augury](https://images.ctfassets.net/23aumh6u8s0i/7bGlZy92HMw8xmawiamiGM/247a435b6c0bce9f27684c5bffa446a7/augury)
 
 [Augury](https://augury.angular.io/) (formerly Batarangle) is a Chrome extension that will help developers debug and understand how their Angular 2 application is running in real time. The app is built by [Rangle.io](http://rangle.io/) and offers a whole suite of features to help developers understand their apps component relationships, get detailed component info as well as understand the component hierarchy. Augury will also help developers understand how routing is affecting their app as well as allow developers to edit component attributes on the fly and see those changes reflected in real time.
 
## Angular 2 Becomes A Platform
 
 If there's one key takeaway from today, it's that Angular 2 is a platform for app development. The core library has been broken up and modularized into logical components, tooling has greatly improved and extending Angular 2 to support other frameworks is becoming a reality. Let's look at some of the other announcements made today.
 
### Native Mobile Applications with NativeScript 2.0
 
 [NativeScript 2.0](https://www.nativescript.org/) was announced today with support for Angular 2. NativeScript 2.0 allows developers to build native mobile applications with Angular 2. Nativescript converts Angular 2 code into the native iOS and Android API calls which are then executed as if you were writing a native mobile application in Objective-C or Java. A huge feature that Nativescript also supports is the ability to use existing native iOS Cocoa Pods and Android Gradle plugins directly in your TypeScript code.
 
### Component Router
 
 The Router in Angular 2 is very powerful. Misko Hevery, the father of Angular, gave a presentation on the new router and how it will improve performance of Angular 2 applications. The Angular 2 Router will only load components when it absolutely needs them. The componetized router also handles the declaration of routes in a unique way. Rather than have a single route definition file that lists all the possible routes your app will have, you declare routes in each of your components. This way, you separate the routing concerns to individual components.
 
## Aside: Auth0's Angular 2 JWT Library
 
 Now is the perfect time to deep your feet into Angular 2 development. If you are building a consumer facing app, you are likely to need a user authentication system. Here at Auth0, we've built a [helper library](https://github.com/auth0/angular2-jwt) for handling JSON Web Token (JWT) authentication. The Angular 2 JWT library can help you integrate JWT authentication with both the Auth0 platform or your own authentication system. If you don't already have an Auth0 account, <a href="https://auth0.com/signup" data-amp-replace="CLIENT_ID" data-amp-addparams="anonId=CLIENT_ID(cid-scope-cookie-fallback-name)">sign up</a> for free and get started today.
 
 If you would like a crash course into Angular 2, check our Ryan Chenkie's Angular 2 series starting with [Angular 2 Pipes](https://auth0.com/blog/2015/09/03/angular2-series-working-with-pipes/).
 
## Conclusion and Additional Resources
 
 Day 1 of ng-conf has been exciting. Angular 2 is shaping up to become a great platform for building both web and mobile applications that can run on both the server and client. This is a highly ambitious goal by the team, but one that seems attainable after today.
 
 To conclude, I'll leave you with a list of additional resources and links to help you both learn Angular 2 and stay up to date with the latest news and announcements.
 
 * [ng-conf Live Stream Day 2](https://www.ng-conf.org/#/) *(starting at 9am PST)* - tune in Day 2 of ng-conf for more talks
 * [Angular 2 Style Guide](https://angular.io/styleguide) - learn Angular 2 best practices
 * [Angular 2 TypeScript Snippets](https://marketplace.visualstudio.com/items?itemName=johnpapa.Angular2) - written by [John Papa](https://twitter.com/John_Papa), a collection of snippets to help you write Angular 2 code faster
 

"ng-conf"