Proposal: Migrate frontend to Angular Signals

Proposal: Migrate frontend to Angular Signals

Hi team,

Since Signals are now stable in Angular 20 and we are planning to upgrade to Angular 20 (#2652) ourselves, I’d like to propose migrating parts of the Juice Shop frontend to use Angular Signals.

Why Signals?

Signals introduce a new reactivity model that is:

• More predictable – Signals provide fine-grained reactivity without relying on change detection zones.
• Better performance – They enable better optimization and reduce unnecessary re-renders.
• Easier to reason about – State flows are clearer and easier to follow, especially in complex UIs.
• Supports Zoneless Angular – Signals are key to running Angular apps without Zone.js, which can improve performance and simplify debugging.
• Framework-aligned – Signals are now a core part of Angular’s direction going forward.

Migration Strategy

We can gradually migrate the codebase by:

1. Starting with simpler components/pages that rely on basic state logic.
2. Gradually adopting Signals in more complex areas as we gain confidence.
3. Avoiding unstable or incomplete features for now (e.g., reactive forms are still under development and not Signal-based yet).

This approach allows us to benefit from Signals today while staying aligned with Angular’s future direction.

I’d be happy to help with this migration effort. Let me know what you think!

Thanks!