Google Releases Angular v22 with Stable Signal Forms, OnPush by Default and Experimental WebMCP

What happened

Google has released Angular v22 of its TypeScript-first framework, centering the cut on API stabilizations, more ergonomic templates, and tooling work aimed at AI integration. The headline items are the stabilization of Signal Forms, improved change detection with OnPush as the default posture, an experimental WebMCP surface, a new @Service() decorator for dependency injection, support for TypeScript 6, and the removal of deprecated features. Those pieces land together as a release that hardens prior reactive and forms work rather than introducing a brand-new application model from scratch.

Signal Forms moving from experimental or preview territory into a stable API is the most concrete product change for everyday feature work. Forms in Angular have long mixed template-driven and reactive styles with their own change-detection costs and mental models. Stabilizing a signals-based forms path ties form state, validation, and UI updates to the same reactive primitives the framework has been steering teams toward for component state. OnPush as the default change-detection strategy reinforces that direction: fewer default full-tree checks, more reliance on explicit signal and input updates to decide what re-renders. The @Service() decorator targets the same ergonomics problem on the DI side by giving a clearer, more declarative way to register and consume services instead of scattering older provider patterns. Experimental WebMCP sits beside tooling enhancements for AI integration, pointing at machine-consumable or agent-facing hooks around the framework surface rather than a finished, production-mandated protocol.

The technical detail

For engineers and builders, the practical impact is migration pressure and opportunity in equal measure. Teams already on signals and careful OnPush usage will find v22 closer to how they already write apps, with fewer dual APIs to defend in reviews. Teams still on default change detection, older forms APIs, or deprecated patterns face a forced inventory: which forms should move to Signal Forms, which components assume broader dirty checking, and which DI and lifecycle usages depend on removed APIs. TypeScript 6 support also couples framework upgrades to the language toolchain, so monorepos that pin older TypeScript must plan compiler, lint, and CI bumps alongside the Angular major. The AI-oriented tooling and experimental WebMCP matter most to shops building generators, copilot-style assistants, or internal scaffolding that need stable, structured access to Angular concepts rather than scraping docs and AST heuristics.

Why it matters for builders

In market context, Angular remains Google’s long-running enterprise and large-app TypeScript framework, competing with React’s ecosystem gravity and Vue’s progressive model while differentiating on batteries-included DI, routing, and forms. Stabilizing Signal Forms and defaulting OnPush is a direct answer to years of criticism that Angular’s reactivity story lagged the fine-grained update models popularized elsewhere. The release does not claim parity on every front, but it signals that the post-Zone, signals-first architecture is no longer a side path. AI tooling and WebMCP experiments also track an industry pattern: frameworks that make their structure legible to agents and generators reduce the cost of greenfield code and large refactors, which is where Angular’s opinionated structure can be an advantage if the tooling is real.

Market and competitive context

The near-term takeaway is to treat v22 as a stabilization major: audit deprecations first, then decide form and change-detection strategy deliberately rather than upgrading only for the version number. Prefer Signal Forms for new form surfaces once the stable API is adopted in your workspace, and assume OnPush-by-default means new components must own their update signals and inputs. Watch whether WebMCP graduates from experimental and whether the AI tooling enhancements become first-class CLI or language-service workflows rather than optional plugins. Also watch how TypeScript 6 support interacts with your build graph, especially shared libraries that still target older compiler options.

What to watch next

Risks and open questions sit mostly around completeness and migration cost. Experimental WebMCP implies the shape and guarantees of that API may change, so early adopters should isolate integrations. Removal of deprecated features will break apps that postponed cleanup; the release notes and automated migrations will matter more than marketing bullets. Open questions include how thoroughly Signal Forms covers advanced multi-step, dynamic, and cross-field cases teams currently solve with custom reactive forms, and whether OnPush as default creates subtle regressions in apps that relied on ambient change detection without noticing. Related prior art is the broader industry shift to signal- or fine-grained reactivity and stricter rendering defaults, which Angular is now encoding as the default product path rather than an advanced opt-in.