Why signals are introduced in Angular - Visual Breakdown

Concept Flow - Why signals are introduced

Old Angular Change Detection

↓

Detect Changes on Entire Component Tree

↓

Performance Issues

↓

Need for Fine-Grained Reactivity

↓

Introduce Signals

↓

Track Dependencies Precisely

↓

Efficient Updates & Better Performance

This flow shows how Angular moved from broad change detection to precise signals for better performance.

Execution Sample

Angular

import { signal } from '@angular/core';
const count = signal(0);
count.set(1);
console.log(count());

This code creates a signal, updates it, and reads its current value.

Execution Table

Step	Action	Signal Value	Effect
1	Create signal with initial value 0	0	Signal initialized
2	Set signal value to 1	1	Signal updated, triggers dependents
3	Read signal value	1	Returns current value 1

💡 Signal value read after update; shows precise tracking and update

Variable Tracker

Variable	Start	After Step 2	Final
count	0	1	1

Key Moments - 2 Insights

Why does Angular need signals instead of old change detection?

Old change detection checks the whole component tree, which can be slow. Signals track only what changes, making updates faster (see execution_table Step 2).

What happens when we set a new value to a signal?

Setting a signal updates its value and notifies only the parts that depend on it, avoiding unnecessary work (see execution_table Step 2).

Visual Quiz - 3 Questions

Look at the execution table, what is the signal value after Step 2?

A 1

B 0

C undefined

D null

💡 Hint

Check the 'Signal Value' column at Step 2 in the execution_table

At which step does the signal notify dependents about a change?

A Step 1

B Step 3

C Step 2

D No notification happens

💡 Hint

See the 'Effect' column in execution_table for Step 2

If we never call set() on the signal, what value does count() return?

A 1

B 0

C undefined

D Error

💡 Hint

Look at the initial signal value in variable_tracker and Step 1 of execution_table

Concept Snapshot

Signals in Angular track specific reactive values.
They replace broad change detection.
Use signal() to create, set() to update, and call() to read.
This leads to faster, precise UI updates.
Signals notify only dependents when changed.

Full Transcript

Angular introduced signals to improve performance by tracking reactive values precisely. Previously, Angular checked the entire component tree for changes, which could slow down apps. Signals hold a value and notify only the parts of the UI that depend on them when the value changes. For example, creating a signal with signal(0) sets its initial value to 0. When we update it with set(1), the signal changes to 1 and triggers updates only where needed. Reading the signal with count() returns the current value. This approach makes Angular apps faster and more efficient.

Practice

1. Why were signals introduced in Angular?

easy

A. To make it easier to track and react to data changes

B. To replace all Angular directives

C. To remove the need for components

D. To simplify CSS styling

Solution

1. Step 1: Understand the purpose of signals

   Signals help Angular track changes in data and update the UI efficiently.

2. Step 2: Compare with other options

   Replacing directives, removing components, or simplifying CSS are unrelated to signals.

3. Final Answer:

   To make it easier to track and react to data changes -> Option A

4. Quick Check:

   Signals improve data tracking = C [OK]

Hint: Signals help track data changes easily [OK]

Common Mistakes:

• Thinking signals replace Angular directives
• Confusing signals with styling tools
• Believing signals remove components

2. Which of the following is the correct way to create a signal in Angular?

easy

A. const count = createSignal(0);

B. const count = new Signal(0);

C. const count = signal(0);

D. const count = signal.create(0);

Solution

1. Step 1: Recall Angular signal syntax

   The correct syntax uses the function signal() to create a signal.

2. Step 2: Check other options

   Options B, C, and D use incorrect constructors or methods not in Angular's signal API.

3. Final Answer:

   const count = signal(0); -> Option C

4. Quick Check:

   Use signal() function to create signals = A [OK]

Hint: Use signal() function to create signals [OK]

Common Mistakes:

• Using new keyword with Signal
• Calling createSignal instead of signal
• Using dot notation like signal.create

3. Given this Angular code snippet:

const count = signal(0);
count.set(5);
console.log(count());

What will be printed in the console?

medium

A. 5

B. undefined

C. signal(0)

D. 0

Solution

1. Step 1: Understand signal creation and update

   The signal count starts at 0, then count.set(5) updates its value to 5.

2. Step 2: Evaluate the console.log output

   Calling count() returns the current value, which is 5 after the update.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   Signal value after set(5) = 5 [OK]

Hint: Calling signal() returns current value [OK]

Common Mistakes:

• Thinking count() returns the initial value
• Confusing signal object with its value
• Expecting undefined without set call

4. What is wrong with this Angular signal code?

const count = signal(0);
count = signal(5);

medium

A. signal() cannot hold numbers

B. signal() must be called with a string

C. count() should be used instead of count

D. Signals cannot be reassigned like this

Solution

1. Step 1: Understand signal immutability

   Signals are constants; you cannot reassign the variable holding a signal.

2. Step 2: Check other options

   signal() accepts numbers, and count() is for reading value, not reassignment.

3. Final Answer:

   Signals cannot be reassigned like this -> Option D

4. Quick Check:

   Signal variables are constant references = A [OK]

Hint: Signals are constants; don't reassign them [OK]

Common Mistakes:

• Trying to reassign signal variables
• Confusing signal creation with value reading
• Thinking signal only accepts strings

5. How do signals improve Angular app performance compared to traditional change detection?

hard

A. By running change detection on the entire app every time

B. By updating only the parts of the UI that depend on changed data

C. By disabling all UI updates until manual refresh

D. By removing the need for templates

Solution

1. Step 1: Understand traditional change detection

   Traditional Angular runs change detection on many components, which can be slow.

2. Step 2: Understand signals' selective update

   Signals update only UI parts that depend on changed data, improving speed and efficiency.

3. Step 3: Evaluate options

   By updating only the parts of the UI that depend on changed data correctly describes signals' selective update. By disabling all UI updates until manual refresh is incorrect because signals do not disable UI updates.

4. Final Answer:

   By updating only the parts of the UI that depend on changed data -> Option B

5. Quick Check:

   Signals update only needed UI parts = B [OK]

Hint: Signals update only affected UI parts [OK]

Common Mistakes:

• Thinking signals disable UI updates
• Believing change detection runs everywhere always
• Assuming signals remove templates