Access modifiers in components in Angular - Performance & Optimization

Performance: Access modifiers in components

MEDIUM IMPACT

Access modifiers affect how component properties and methods are exposed, impacting template binding and change detection performance.

Controlling component property visibility to optimize change detection

Angular

export class MyComponent {
  private data = [];
  updateData() {
    // update logic
  }
}

Private properties are not bound in templates, reducing Angular's change detection scope and improving responsiveness.

📈 Performance GainReduces change detection checks, lowering INP latency and improving input responsiveness.

Controlling component property visibility to optimize change detection

Angular

export class MyComponent {
  public data = [];
  public updateData() {
    // update logic
  }
}

Public properties and methods are accessible in the template, causing Angular to watch them for changes, increasing change detection cost.

📉 Performance CostTriggers change detection checks on all public members, increasing INP latency especially in large components.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Public properties bound in template	High (many bindings)	Medium (due to frequent updates)	Medium	[X] Bad
Private properties not bound in template	Low (fewer bindings)	Low	Low	[OK] Good

Rendering Pipeline

Access modifiers influence which component properties Angular binds to templates. Public members are watched during change detection, affecting the update cycle.

→Change Detection

→Template Binding

⚠️ BottleneckChange Detection

Core Web Vital Affected

INP

Access modifiers affect how component properties and methods are exposed, impacting template binding and change detection performance.

Optimization Tips

1Use private or protected modifiers for properties not used in templates.

2Avoid exposing unnecessary public properties to reduce change detection scope.

3Keep template bindings minimal to improve input responsiveness.

Performance Quiz - 3 Questions

How do public access modifiers on component properties affect Angular's change detection?

A They prevent Angular from checking those properties.

B They increase the number of properties Angular checks during change detection.

C They reduce the template size.

D They have no effect on change detection.

DevTools: Performance

How to check: Record a performance profile while interacting with the component. Look for long change detection cycles.

What to look for: High time spent in 'Change Detection' indicates too many public bindings causing slow responsiveness.

Practice

1. Which access modifier allows a component property to be used directly in its template in Angular?

easy

A. readonly

B. private

C. protected

D. public

Solution

1. Step 1: Understand template access rules

   Angular templates can only access properties and methods marked as public.

2. Step 2: Compare access modifiers

   private and protected members are not accessible in templates, only public members are.

3. Final Answer:

   public -> Option D

4. Quick Check:

   Templates access public members only [OK]

Hint: Templates can only see public members [OK]

Common Mistakes:

• Thinking private members are accessible in templates
• Confusing protected with public for template access
• Assuming readonly affects visibility

2. Which of the following is the correct syntax to declare a private property named count in an Angular component?

easy

A. count private: number;

B. private count: number;

C. protected count = number;

D. public count: number;

Solution

1. Step 1: Recall TypeScript property declaration syntax

   Access modifier comes first, then property name, colon, and type.

2. Step 2: Check each option

   private count: number; matches correct syntax: private count: number;. public count: number; is public, not private. protected count = number; has wrong assignment syntax. count private: number; has wrong order.

3. Final Answer:

   private count: number; -> Option B

4. Quick Check:

   Access modifier + name + colon + type [OK]

Hint: Access modifier comes before property name [OK]

Common Mistakes:

• Placing access modifier after property name
• Using assignment instead of type annotation
• Mixing up protected and private keywords

3. Consider this Angular component snippet:

export class MyComponent {
  private secret = 'hidden';
  public visible = 'shown';
}

Which property can be accessed in the component's template?

medium

A. secret

B. Both secret and visible

C. visible

D. Neither secret nor visible

Solution

1. Step 1: Identify access modifiers of properties

   secret is private, visible is public.

2. Step 2: Recall template access rules

   Templates can only access public members, so only visible is accessible.

3. Final Answer:

   visible -> Option C

4. Quick Check:

   Only public properties are template-accessible [OK]

Hint: Only public properties show in templates [OK]

Common Mistakes:

• Assuming private properties are accessible in templates
• Thinking both properties are accessible
• Confusing private with protected

4. Identify the error in this Angular component code:

export class DemoComponent {
  private title = 'Hello';
}

// In template:
// <h1>{{ title }}</h1>

medium

A. Template cannot access private property 'title'

B. No error, code works fine

C. Missing semicolon after title declaration

D. title should be declared as protected

Solution

1. Step 1: Check property access modifier

   title is declared private, so it is hidden from outside the class.

2. Step 2: Understand template access rules

   Angular templates can only access public properties, so trying to use title in template causes an error.

3. Final Answer:

   Template cannot access private property 'title' -> Option A

4. Quick Check:

   Private properties are not accessible in templates [OK]

Hint: Templates only see public, not private properties [OK]

Common Mistakes:

• Ignoring access modifier effect on templates
• Thinking missing semicolon causes error
• Confusing protected with private for template access

5. You want a property data in a base Angular component to be accessible in its child components but not directly in the template. Which access modifier should you use?

hard

A. protected

B. private

C. public

D. readonly

Solution

1. Step 1: Understand access modifier meanings

   private hides from all except the class itself, public exposes everywhere including templates, protected allows access in the class and its subclasses but not templates.

2. Step 2: Match requirement to modifier

   Since data should be accessible in child components but hidden from templates, protected fits perfectly.

3. Final Answer:

   protected -> Option A

4. Quick Check:

   Protected = accessible in children, hidden from templates [OK]

Hint: Use protected for child access, hide from templates [OK]

Common Mistakes:

• Choosing public and exposing property to templates
• Using private and blocking child access
• Confusing readonly with access control