December 15th, 2015
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.
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.
Get going now with the updated and expanded Quickstart and Tutorial on angular.io. From there, you can check out several developer guides and a handy cheatsheet covering the main features in Angular 2.
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
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.
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.
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.
We’ve also recently added a mechanism for submitting feedback for all pages. Just click on the exclamation point icon in the upper right of the page and tell us what could be improved.
What comes next?
We’re already hard at work on the set of improvements to move Angular 2 to its full and final release. While we will make many small improvements, the big ones for final are:
- Reducing Angular 2’s payload size.
- Making the Angular CLI usable end to end throughout the development process.
- Creating a more developer-friendly route definition and link API for the Component Router.
- Support for animations.
- I18n and L10n support.
And there are even more cool things to come — some we’ve already started on including:
- More documentation, particularly around ES5/ES6 usage.
- Even better startup and runtime performance
- An architectural style guide
- Unit and end-to-end testing improvements
- More support for mobile web and installable mobile apps
- Material Design components for Angular 2
- A tools platform for deep IDE support
- Better support for ES6 and Babel
Thanks, and we’re looking forward to seeing the apps you build appear on madewithangular.com!