Angular 2 Beta

We’re ecstatic to announce that we’ve reached Angular 2 Beta. You can read about many of the improvements over Angular 1 in a recent post. Get started learning Angular 2 now at angular.io.

What does ‘beta’ mean?

Beta means we’re now confident that most developers can be successful building large applications using Angular 2.

Through developer preview and alpha we’ve worked closely with several large projects here at Google including AdWords, GreenTea (Google’s internal CRM system), and Google Fiber. In fact, just a few weeks ago we saw Google Fiber launch on their new Angular 2 code base.

Externally, we’ve worked closely with several other teams integrating with Angular 2 including Ionic Framework on Ionic 2, Telerik on NativeScript, Rangle.io on Batarangle, and many others.

We’ve incorporated the majority of feedback from these teams that would create breaking changes. Given this, we’re looking forward to other teams developing in earnest and telling us how we can help.

While the many in-progress Angular 2 books and courses will likely take a few weeks to catch up to the latest changes, we can recommend taking a look at the clear explanations and examples on the thoughtram blog and this in depth primer on Angular 2.

Upgrading from Angular 1

You may have an Angular 1 app today and you want to start writing Angular 2 code in that app, without changing your working/tested angular 1 code. This is where ngUpgrade comes in.

While you can upgrade apps in a “big bang” approach where you halt production until everything is rewritten, we’re supporting two paths for where teams want to upgrade their Angular 1 apps to Angular 2.

ngUpgrade

We know many of you made large investments in Angular 1 and have created some awesome apps. We created ngUpgrade for all of you to make it possible to leverage your existing apps and move forward with Angular 2.

ngUpgrade lets you mix Angular 2 into your existing Angular 1 application. You’ll get to take advantage of Angular 2’s improved speed and APIs immediately as you replace components a bit at a time over the course of your releases. Learn more in this article from thoughtram and the upgrade guide in our docs.

ngForward

Some teams, with apps that are more sensitive to download size, will want to avoid having both Angular 1 and Angular 2 libraries running in their app simultaneously. For this, we have ngForward which lets you write Angular 1 applications in the syntax of Angular 2. This lets your team get used Angular 2 conventions and styles in your apps today and shorten the distance to doing the full upgrade to Angular 2 when you’re ready.