Angular released its latest 2022 Developer Survey Report for Angular Users, based on feedback from 12,000 developers . The survey found:
- More than 82% of developers said they were satisfied with Angular; 89% of developers were satisfied with how the different components of Angular worked together before, an increase from 85% in 2021.
- Nearly 70% of developers are using the latest two versions of the framework, with only 9% using v11 or earlier.
- Most people learn about the latest Angular features from social media and Angular websites, followed by blogs, online communities such as StackOverflow, and online education sites
Respondents' favorite Angular feature was dependency injection, followed by IDE support, CLI build tools, and keeping up with Angular versions. The areas they identified as most in need of improvement are server-side rendering, testing, debugging and profiling, initial load performance, and component authoring formats.
Additionally, the Angular team explored something that corresponds to its roadmap:
- Documentation and Sample Code - To address this feedback, they developed a new getting started tutorial that walks through the concepts step by step. Documentation content has also been reviewed for missing topics and opportunities for improvement. Expect plenty of new content in the next year about standalone components, server-side rendering, existing theme revisions and cleanups.
- Server-Side Rendering — Provides a range of improvements, such as a developer preview of hydration and compatibility with workers for edge rendering. Next, the development team plans to explore partial hydration and better integration of Angular Universal with the CLI.
- Initial load performance — Server-side rendering often slows down initial load time due to the faster LCP. Another feature the Angular team revealed it is currently working on is a more ergonomic component-level code-splitting API that will allow you to declaratively annotate parts of the component tree that should be lazy-loaded. An update is expected in the coming weeks.
- Testing — The Angular development team is replacing Karma in the Angular CLI with the Web Test Runner for in-browser testing and adding support for Jest.
- Debugging and Profiling - Continued work with Chrome DevTools to improve stack traces released in Angular 15 in November. As well as an ongoing effort to develop better tools for understanding dependency injection and routing structures in Angular DevTools.
- Runtime Performance — Angular 16 introduces a new reactive system in Angular via signals. The team plans to improve the runtime performance of applications using signals without manual optimization and better Core Web Vitals.
- Component authoring format — Angular 16 provides the required inputs and self-closing tags. Now the development team is working on input coercion and improvements in the control flow.
More details can be found on the official blog .