Keyframe animations in Angular - Performance & Optimization

Performance: Keyframe animations

MEDIUM IMPACT

Keyframe animations affect the smoothness of visual transitions and can impact the browser's paint and composite stages, influencing user experience during animations.

Animating an element's position smoothly without causing layout shifts

Angular

import { animate, keyframes, style, transition, trigger } from '@angular/animations';

export const slideAnimation = trigger('slide', [
  transition(':enter', [
    animate('500ms ease-in', keyframes([
      style({ transform: 'translateX(0)', offset: 0 }),
      style({ transform: 'translateX(100px)', offset: 1 })
    ]))
  ])
]);

Animating 'transform' uses the compositor thread, avoiding layout recalculations and reducing jank.

📈 Performance GainNo reflows triggered, only compositing; reduces CPU load and prevents CLS.

Animating an element's position smoothly without causing layout shifts

Angular

import { animate, keyframes, style, transition, trigger } from '@angular/animations';

export const slideAnimation = trigger('slide', [
  transition(':enter', [
    animate('500ms ease-in', keyframes([
      style({ left: '0px', offset: 0 }),
      style({ left: '100px', offset: 1 })
    ]))
  ])
]);

Animating 'left' triggers layout recalculations and reflows causing jank and layout shifts.

📉 Performance CostTriggers 1 reflow and 1 repaint per animation frame, increasing CPU usage and causing CLS.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Animating 'left' property	Multiple style updates	Triggers reflow every frame	High paint cost due to layout changes	[X] Bad
Animating 'transform' property	Style updates only	No reflows triggered	Low paint cost, uses compositor	[OK] Good

Rendering Pipeline

Keyframe animations update styles over time. Animations on layout-affecting properties cause Style Calculation, Layout, Paint, and Composite stages repeatedly. Animations on transform or opacity skip Layout and Paint, going directly to Composite.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckLayout and Paint stages are most expensive when animating layout properties.

Core Web Vital Affected

CLS

Keyframe animations affect the smoothness of visual transitions and can impact the browser's paint and composite stages, influencing user experience during animations.

Optimization Tips

1Animate only transform and opacity properties for best performance.

2Avoid animating layout-affecting properties like left, width, margin.

3Use Angular's animation API with keyframes that target GPU-accelerated properties.

Performance Quiz - 3 Questions

Which CSS property is best to animate for smooth performance in Angular keyframe animations?

A width

B left

C transform

D margin

DevTools: Performance

How to check: Record a performance profile while the animation runs. Look for Layout and Paint events during animation frames.

What to look for: High frequency of Layout and Paint events indicates poor animation performance; absence means optimized animation.

Practice

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

easy

A. To manage component data binding

B. To create smooth, multi-step visual changes in components

C. To handle HTTP requests efficiently

D. To define routing paths in the app

Solution

1. Step 1: Understand what keyframe animations do

   Keyframe animations allow defining multiple steps of style changes over time, creating smooth transitions.

2. Step 2: Identify Angular's use of keyframes

   Angular uses keyframes inside the animate function to control detailed animation steps.

3. Final Answer:

   To create smooth, multi-step visual changes in components -> Option B

4. Quick Check:

   Keyframe animations = smooth multi-step visual changes [OK]

Hint: Keyframes control step-by-step visual changes [OK]

Common Mistakes:

• Confusing animations with data handling
• Thinking keyframes manage routing
• Mixing animations with HTTP requests

2. Which of the following is the correct syntax to import keyframe animation functions in Angular?

easy

A. import { keyframes, animate } from '@angular/animations';

B. import { keyframe, animation } from '@angular/core';

C. import { animateKeyframes } from '@angular/animations';

D. import { keyframes, animate } from '@angular/core';

Solution

1. Step 1: Identify the correct Angular package for animations

   Angular animations functions like keyframes and animate are imported from '@angular/animations'.

2. Step 2: Check the exact function names and import syntax

   The correct functions are keyframes and animate, imported with curly braces from '@angular/animations'.

3. Final Answer:

   import { keyframes, animate } from '@angular/animations'; -> Option A

4. Quick Check:

   Correct import = import { keyframes, animate } from '@angular/animations'; [OK]

Hint: Animations import from '@angular/animations' with exact names [OK]

Common Mistakes:

• Importing from '@angular/core' instead of '@angular/animations'
• Using wrong function names like 'keyframe' or 'animation'
• Missing curly braces in import statement

3. Given the Angular animation code below, what will be the final background color after the animation completes?

animate('2s', keyframes([
  style({ backgroundColor: 'red', offset: 0 }),
  style({ backgroundColor: 'blue', offset: 0.5 }),
  style({ backgroundColor: 'green', offset: 1 })
]))

medium

A. red

B. blue

C. transparent

D. green

Solution

1. Step 1: Understand keyframe offsets and colors

   The animation starts at red (offset 0), changes to blue at halfway (offset 0.5), and ends at green (offset 1).

2. Step 2: Determine final style after animation

   At offset 1 (end), the background color is green, so the final color after animation is green.

3. Final Answer:

   green -> Option D

4. Quick Check:

   Final offset color = green [OK]

Hint: Final offset (1) style is final animation state [OK]

Common Mistakes:

• Choosing the first or middle color instead of final
• Confusing offset values with time
• Assuming default color remains after animation

4. Identify the error in this Angular animation code snippet:

trigger('fadeIn', [
  transition(':enter', [
    animate('1s', keyframes([
      style({ opacity: 0, offset: 0 }),
      style({ opacity: 1 })
    ]))
  ])
])

medium

A. Incorrect trigger name syntax

B. animate duration should be a number, not a string

C. Missing offset value in second style inside keyframes

D. transition selector ':enter' is invalid

Solution

1. Step 1: Check keyframe style objects for offsets

   Each style in keyframes should have an offset between 0 and 1 to define timing precisely.

2. Step 2: Identify missing offset

   The second style lacks an offset property, which is required for keyframes to work correctly.

3. Final Answer:

   Missing offset value in second style inside keyframes -> Option C

4. Quick Check:

   All keyframe styles need offset [OK]

Hint: Every keyframe style needs an offset between 0 and 1 [OK]

Common Mistakes:

• Omitting offset in some keyframe styles
• Using wrong transition selectors
• Passing duration as number instead of string

5. You want to create an Angular animation that moves an element from left to right and changes its opacity from 0 to 1 in 3 seconds, with three key steps: start (left: 0px, opacity: 0), middle (left: 50px, opacity: 0.5), and end (left: 100px, opacity: 1). Which of the following keyframes arrays correctly implements this?

hard

A. [
style({ left: '0px', opacity: 0, offset: 0 }),
style({ left: '50px', opacity: 0.5, offset: 0.5 }),
style({ left: '100px', opacity: 1, offset: 1 })
]

B. [
style({ left: 0, opacity: 0 }),
style({ left: 50, opacity: 0.5 }),
style({ left: 100, opacity: 1 })
]

C. [
style({ left: '0px', opacity: 0 }),
style({ left: '50px', opacity: 0.5, offset: 0.5 }),
style({ left: '100px', opacity: 1, offset: 1 })
]

D. [
style({ left: '0px', opacity: 0, offset: 0 }),
style({ left: '50px', opacity: 0.5 }),
style({ left: '100px', opacity: 1, offset: 1 })
]

Solution

1. Step 1: Verify all keyframe styles have offsets

   Each style must have an offset between 0 and 1 to define animation timing precisely.

2. Step 2: Check property values and units

   Left positions must be strings with units like 'px'. [ style({ left: '0px', opacity: 0, offset: 0 }), style({ left: '50px', opacity: 0.5, offset: 0.5 }), style({ left: '100px', opacity: 1, offset: 1 }) ] correctly uses '0px', '50px', '100px' and includes all offsets.

3. Step 3: Identify the correct option

   [ style({ left: '0px', opacity: 0, offset: 0 }), style({ left: '50px', opacity: 0.5, offset: 0.5 }), style({ left: '100px', opacity: 1, offset: 1 }) ] has all offsets and correct units; others miss offsets or units, making them invalid.

4. Final Answer:

   Option A with all offsets and px units -> Option A

5. Quick Check:

   Offsets + units correct = [ style({ left: '0px', opacity: 0, offset: 0 }), style({ left: '50px', opacity: 0.5, offset: 0.5 }), style({ left: '100px', opacity: 1, offset: 1 }) ] [OK]

Hint: All keyframes need offsets and units for position values [OK]

Common Mistakes:

• Missing offset properties in some keyframes
• Using numbers without units for CSS properties
• Partial offsets causing animation errors