Angular Signal Forms — Set-up and validation rules

The article explains Angular’s experimental Signal Forms (introduced with Angular 21), showing how they provide a third approach to building forms alongside template-driven and reactive forms by using signals to manage form data, state, and validation more directly and intuitively, including centralized, reusable validation rules and simpler access to field status like validity, errors, and user interaction.

What’s new in Angular 21.1?

Angular 21.1 is out, and while most of the new features are still experimental, the release gives us a solid preview of where Angular is heading. From Signal Forms API changes and long-awaited focus helpers, to more flexible control flow, template improvements, router updates, and MCP server enhancements, this version is packed with ideas worth exploring—just not shipping to production yet. Let’s take a quick look at what’s new and what’s promising.

Anti-pattern series: Not unsubscribing from Observables

This article explains how Angular 16 improves observable cleanup using takeUntilDestroyed and recommends applying it in services rather than components, so all subscribers are automatically protected from memory leaks.

How to animate transitions with Angular?

Angular 20.2 introduces a delightfully simple way to animate elements as they enter and leave the screen. With zero imports and CSS doing all the heavy lifting, the new animate.enter and animate.leave attributes let you add smooth, modern transitions with minimal code and maximum sanity.

Dynamic component creation with Angular

The article explains how to create and control Angular components dynamically at runtime, rather than relying on static components that are toggled visible/hidden in the DOM.

Angular 21 is available!

Angular 21 has been released, and I’m going to divide the new features into different categories, since a lot of the new features are experimental and not recommended for production use yet.

Use Lighthouse to improve your Angular applications

Angular developers often focus on code structure and framework mastery—but end users care most about speed, accessibility, and visibility. This article highlights how tools like Google Chrome’s built-in Lighthouse can help you measure and improve your app’s performance, accessibility, and SEO. By running quick audits and reviewing actionable insights, developers can bridge the gap between technical excellence and real-world user experience.

Subject, BehaviorSubject, and ReplaySubject

Angular’s reactive world revolves around Subjects, but the star is often the BehaviorSubject — why? Because it always starts with a value, and when you subscribe, you immediately get the latest emission (like receiving the current issue of a magazine). Meanwhile, ReplaySubject lets you go further by replaying multiple past values (no default), and a plain Subject is just “live only” — no past, no future. Let’s dig into when and why to use each.

Signals + HTTP = httpResource [Tutorial]

Angular 19.2 rolls out httpResource — an experimental, signal-friendly layer over HttpClient that lets you fetch data reactively. Instead of juggling Observables and state flags, httpResource gives you built-in signals like isLoading() and hasValue(), and it automatically re-fires requests when dependent signals (e.g. page number, query) change.