DEV Community

Cover image for State of Angular - Highlights from Google I/O

State of Angular - Highlights from Google I/O

Google I/O is a developer conference held by Google. "I/O" stands for Input/Output, as well as the slogan "Innovation in the Open".

Google has concluded its two-hour I/O keynote, which was jam-packed with information. AI, Android, and, of course, a slew of Pixel hardware were all mentioned.

This is just to say that there is a whole lot more than what I am summarizing in this post.

Here we will focus on Angular and the future of this framework.

State of Angular

1. Ivy Engine

The Angular team rewrote from the ground up Angular's runtime and compiler so that apps are now powered by the better, more efficient Ivy rendering engine.
Here are some of the advantages offered by the Ivy Engine:

2. Standalone Components

On the Angular blog, we can read that the goal of Standalone components is "to reduce boilerplate and make Angular easier to use and learn by making it possible to build components and applications without NgModules."

This is important because, among other things, it wants to make it easier to learn Angular for new developers!

Another point worth mentioning is that Standalone components will reduce the boilerplate in several cases.

3. New Getting Started

For developers new to the framework, the Angular team is designing a new Getting Started path.

Image description

This is very good news because the current learning path is quite steep, especially for new developers.

My little Angular tutorial might soon become obsolete. But if there is something better out there, it will surely benefit the entire community.

4. TypeScript Everywhere

As you may know, Angular is an opinionated framework with best practices built-in by default.

Angular strives to maintain strong defaults and best practices. To support this vision, and following developers' most requested feature, Angular is adding support for typed forms in Angular templates.

Image description

5. Scalability

Angular made somehow clear that, despite being an opinionated framework, it can support different needs:

  • Indie Developers: The new Standalone Component makes it easier to start without too much boilerplate. The CLI already makes creating a new Angular app, components, and other things very easy as ng new.
  • Startups: Angular Language Service guarantees that developers produce consistent code. Developers can discover mistakes before they are deployed thanks to typing and tooling.
  • Scaleups: Internationalization and progressive web apps (PWA) will come useful. Moreover, being opinionated it is easy to start to work on a different project and know exactly what it will look like.
  • Big organizations: Microfrontends as the next steps?

In all of this, it is fairly easy to update Angular every time a new major version comes out, or more frequently, by using

6. Improved Accessibility

This is a new feature that allows defining unique page titles more simply. This is addressing a common accessibility issue in web frameworks.

7. New commands

More diagnostics help code editors to warn developers of common mistakes before deployment. Here we have two new CLI commands:

  • ng analytics: a way to control and print analytics settings
  • ng cache: a way to control and print cache information


The talks conclude with "There's never been a better time to be an Angular developer".
At a minimum, this is a very cool moment to use Angular in your projects!

Discussion (5)

jwp profile image
John Peters

Really glad to hear we don't need Ngmodules. Too bad it took them so long to update to ECMA 2017 module system.

The other major miss was related to producing, publishing, and consuming web components.

These two concerns alone was the reason I got off Angular after 7 years.

lorenzojkrl profile image
Lorenzo Zarantonello Author

What are you using nowadays?
And what are the differences with Angular?
If you don't mind me asking.

jwp profile image
John Peters

Plain Html5 webcomponents.

Thread Thread
lorenzojkrl profile image
Lorenzo Zarantonello Author

How does that work? What is the benefit compared to a framework/library?
Angular templates can also be plain html.
Same with React.

Thread Thread
jwp profile image
John Peters

Yes both Angular and React were around before Webcomponents. Both of them implemented the same concept in their own opinionated ways. Both are not necessary any longer either. Good news for those that want to get closer to the metal.