Suggest an editImprove this articleRefine the answer for “When were signals introduced in Angular?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**Signals** appeared in Angular in version 16 (May 2023) as a developer preview, and in Angular 17 they became a full part of the new reactive model and the base for template reactivity without Zone.js. **Key point:** signals are the Angular team's official direction toward replacing part of RxJS's functionality in local state and component reactivity.Shown above the full answer for quick recall.Answer (EN)ImageSignals appeared in Angular **in version 16 (May 2023)** as a developer preview, and in **Angular 17** they became a full part of the new reactive model and the base for template reactivity without Zone.js. Brief timeline: | Version | What happened | |---|---| | **Angular 16** | `signal`, `computed`, `effect` appeared, a preview implementation | | **Angular 17** | Signals became the basis of the updated renderer and template reactivity | | **Angular 18 (plan/roadmap)** | A move toward fully dropping `Zone.js` and RxJS in templates | So signals are the Angular team's official direction toward replacing part of RxJS's functionality in local state and component reactivity. If needed, I can explain **why Google introduced signals at all and which Angular problems they solved**.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.