Transition between states in Angular - Performance & Optimization

Performance: Transition between states

MEDIUM IMPACT

This affects how smoothly the UI updates when components change state, impacting user interaction responsiveness and visual stability.

Animating UI changes between component states

Angular

import { Component } from '@angular/core';
import { trigger, state, style, animate, transition } from '@angular/animations';
@Component({
  selector: 'app-good-transition',
  template: `<div [@fadeInOut]="isVisible ? 'visible' : 'hidden'" (click)="toggle()">Content</div>`,
  animations: [
    trigger('fadeInOut', [
      state('visible', style({ opacity: 1 })),
      state('hidden', style({ opacity: 0 })),
      transition('visible <=> hidden', animate('300ms ease-in-out'))
    ])
  ]
})
export class GoodTransitionComponent {
  isVisible = true;
  toggle() {
    this.isVisible = !this.isVisible;
  }
}

Angular animations run on the compositor thread, reducing layout recalculations and providing smooth transitions.

📈 Performance GainSingle composite layer update per transition, reducing reflows and improving INP and CLS.

Animating UI changes between component states

Angular

import { Component } from '@angular/core';
@Component({
  selector: 'app-bad-transition',
  template: `<div [style.opacity]="isVisible ? '1' : '0'" (click)="toggle()">Content</div>`,
})
export class BadTransitionComponent {
  isVisible = true;
  toggle() {
    this.isVisible = !this.isVisible;
  }
}

Directly changing styles without Angular animations causes abrupt changes and triggers multiple layout recalculations.

📉 Performance CostTriggers multiple reflows and repaints on each toggle, causing janky UI and higher INP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Direct style changes on state toggle	Minimal DOM ops	Multiple reflows per toggle	High paint cost due to layout changes	[X] Bad
Angular animations with opacity transitions	Minimal DOM ops	No reflows, only composite	Low paint cost, GPU accelerated	[OK] Good

Rendering Pipeline

State transitions using Angular animations flow through style calculation, layout, paint, and composite stages. Proper animations minimize layout and paint work by using opacity and transform properties.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckLayout and Paint stages are most expensive if transitions trigger reflows.

Core Web Vital Affected

INP, CLS

This affects how smoothly the UI updates when components change state, impacting user interaction responsiveness and visual stability.

Optimization Tips

1Animate opacity or transform properties to avoid layout recalculations.

2Use Angular's animation API to leverage GPU compositing.

3Avoid direct style changes that trigger reflows during state transitions.

Performance Quiz - 3 Questions

Which CSS property is best to animate for smooth Angular state transitions?

A top

B opacity

C width

D margin

DevTools: Performance

How to check: Record a performance profile while toggling the state. Look for layout and paint events in the flame chart.

What to look for: Fewer layout and paint events and more composite-only updates indicate better performance.

Practice

1. What is the main purpose of using transition in Angular animations?

easy

A. To style HTML elements without animation

B. To create a new component

C. To define how the animation moves between two states

D. To fetch data from a server

Solution

1. Step 1: Understand Angular animation components

   Angular animations use trigger, state, and transition to control animations.

2. Step 2: Identify the role of transition

   transition defines how the animation changes from one state to another, specifying timing and style changes.

3. Final Answer:

   To define how the animation moves between two states -> Option C

4. Quick Check:

   Transition controls animation between states = D [OK]

Hint: Transition defines animation flow between states [OK]

Common Mistakes:

• Confusing transition with component creation
• Thinking transition fetches data
• Assuming transition only styles without animation

2. Which of the following is the correct syntax to define a transition from state 'open' to 'closed' in Angular animations?

easy

A. transition('open => closed', [animate('500ms')])

B. transition(open to closed, animate(500ms))

C. transition('open - closed', animate('500'))

D. transition('open > closed', [animate('500ms')])

Solution

1. Step 1: Recall Angular transition syntax

   Transitions use string format with arrow '=>' between states and an array of animation steps.

2. Step 2: Match correct syntax

   transition('open => closed', [animate('500ms')]) uses correct arrow '=>' and wraps animation in an array with timing string '500ms'.

3. Final Answer:

   transition('open => closed', [animate('500ms')]) -> Option A

4. Quick Check:

   Correct arrow and array syntax = A [OK]

Hint: Use 'state1 => state2' with array for animations [OK]

Common Mistakes:

• Using wrong arrow symbols like 'to' or '-'
• Not wrapping animate() in an array
• Missing quotes around states

3. Given this Angular animation trigger:

trigger('openClose', [
  state('open', style({ height: '200px' })),
  state('closed', style({ height: '100px' })),
  transition('open => closed', [animate('300ms ease-out')]),
  transition('closed => open', [animate('300ms ease-in')])
])

What will happen when the component's state changes from 'closed' to 'open'?

medium

A. The height instantly changes to 200px without animation

B. The height animates from 100px to 200px over 300ms with ease-in timing

C. The height animates from 200px to 100px over 300ms with ease-out timing

D. No animation occurs because transition is missing

Solution

1. Step 1: Identify the transition for 'closed => open'

   The trigger defines a transition from 'closed' to 'open' with animation '300ms ease-in'.

2. Step 2: Understand animation effect

   The height changes from 100px (closed) to 200px (open) smoothly over 300ms using ease-in timing.

3. Final Answer:

   The height animates from 100px to 200px over 300ms with ease-in timing -> Option B

4. Quick Check:

   Closed to open triggers 300ms ease-in animation = B [OK]

Hint: Match transition direction to animation timing [OK]

Common Mistakes:

• Confusing animation direction and timing
• Assuming instant style change without animation
• Mixing up 'open => closed' with 'closed => open'

4. Consider this Angular animation code snippet:

trigger('toggle', [
  state('on', style({ opacity: 1 })),
  state('off', style({ opacity: 0 })),
  transition('on <=> off', animate('400ms ease-in-out'))
])

Why might this code cause an error or unexpected behavior?

medium

A. The animate() call is not wrapped in an array

B. The animate() function is missing duration units

C. The states 'on' and 'off' are not defined properly

D. The transition should be inside the state definitions

Solution

1. Step 1: Check animation steps format

   Angular transitions require animation steps like animate() to be wrapped in an array [].

2. Step 2: Verify other parts

   States are properly defined, 'on <=> off' is valid for bidirectional transitions, duration '400ms ease-in-out' has units, and transition is correctly placed outside states.

3. Final Answer:

   The animate() call is not wrapped in an array -> Option A

4. Quick Check:

   Missing array brackets around animate() = C [OK]

Hint: Always wrap animate() in [] array in transitions [OK]

Common Mistakes:

• Not wrapping animate() in an array
• Thinking animate() needs units missing
• Placing transitions inside state definitions

5. You want to create an Angular animation that smoothly toggles a panel's visibility with these states: - 'visible' with opacity 1 and height 'auto' - 'hidden' with opacity 0 and height 0 You also want the height to animate properly even though 'auto' is not animatable directly. Which approach correctly handles this transition?

hard

A. Animate opacity only and skip height animation since 'auto' can't animate

B. Use 'void <=> *' transition with 'style' and 'animate' to animate height from 0 to *

C. Use 'transition('visible => hidden', animate('300ms'))' only without height styles

D. Set height to fixed pixel values in states and animate between them

Solution

1. Step 1: Understand height animation limitations

   CSS cannot animate height from '0' to 'auto' directly because 'auto' is not a numeric value.

2. Step 2: Use fixed pixel heights for animation

   Setting explicit pixel heights (e.g., '0px' and '200px') in states allows smooth height animation between numeric values.

3. Final Answer:

   Set height to fixed pixel values in states and animate between them -> Option D

4. Quick Check:

   Animate numeric heights, not 'auto' = A [OK]

Hint: Animate numeric heights, not 'auto' for smooth transitions [OK]

Common Mistakes:

• Trying to animate height from 0 to 'auto'
• Ignoring height animation and only animating opacity
• Using void transitions incorrectly for this case