Angular without Zone: when the future becomes the default

For years, ngZone served as Angular's autopilot. Handy for triggering change detection, but at the cost of unnecessary re-renders, loose control over state, and applications that slowed down without us always knowing why. We long talked about the day Angular would finally do without all that. That day has come.

With Angular 22, zoneless is no longer an option for the curious — it's the default. zone.js disappears from new projects, OnPush becomes the standard behaviour, and reactivity runs entirely through signals. Around them, a whole ecosystem has matured: Signal Forms, the resource and httpResource APIs for reactive data fetching, and a control flow (@if, @for, @switch) now built into the language. In this session, we'll build a truly zoneless Angular 22 application together, with demos and running code. We'll see how to think in signals rather than detection cycles, how to migrate an existing project smoothly (because the real work is modernising, not starting from scratch), and which pitfalls to avoid along the way. We'll also keep an eye on what's coming at the end of the year and beyond, with selectorless components and the Mutations API.

You'll leave with a clear signal-first mental model, concrete recipes for adopting zoneless on an existing project without breaking everything, and what you need to approach the next Angular version with confidence.