Angular Signals: A Practical Introduction

Placeholder post. This article is a structural example for the solodev collection. It intentionally has no German translation yet, to demonstrate that not every post needs one — translationOf is simply omitted.

Angular signals give you a simpler mental model for reactive state than a full RxJS pipeline, for the cases where you don’t need RxJS’s operators.

When to reach for a signal instead of an Observable

• Local component state that doesn’t need to be composed with async streams.
• Derived values that should recompute automatically when their inputs change.
• Anywhere you’d otherwise reach for BehaviorSubject purely to hold a current value.

A minimal example

import { signal, computed } from "@angular/core";

const count = signal(0);
const doubled = computed(() => count() * 2);

count.set(5);
console.log(doubled()); // 10

(A real version of this post would go deeper into effects, signal-based inputs, and interop with existing RxJS code — left out here since this is a placeholder.)