Smart and dumb component pattern in Angular - Performance & Optimization

Performance: Smart and dumb component pattern

MEDIUM IMPACT

This pattern affects rendering speed and interaction responsiveness by separating data handling from UI rendering.

Separating data fetching and UI rendering in Angular components

Angular

import { Component, Input } from '@angular/core';

@Component({
  selector: 'app-user-display',
  template: `<div>{{user?.name}}</div>`
})
export class UserDisplayComponent {
  @Input() user: any;
}

@Component({
  selector: 'app-user-container',
  template: `<app-user-display [user]="user"></app-user-display>`
})
export class UserContainerComponent {
  user = null;

  constructor() {
    fetch('https://api.example.com/user')
      .then(res => res.json())
      .then(data => this.user = data);
  }
}

Separates data fetching in the smart container component and UI rendering in the dumb component, reducing re-renders and improving maintainability.

📈 Performance GainReduces unnecessary re-renders and isolates UI updates, improving INP and reducing layout thrashing.

Separating data fetching and UI rendering in Angular components

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-user',
  template: `<div>{{user?.name}}</div>`
})
export class UserComponent {
  user = null;

  constructor() {
    fetch('https://api.example.com/user')
      .then(res => res.json())
      .then(data => this.user = data);
  }
}

Combining data fetching and UI rendering causes the component to re-render fully on data change and mixes concerns, leading to harder maintenance and potential performance issues.

📉 Performance CostTriggers full component re-render on data fetch, increasing INP and causing potential layout thrashing.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Smart and dumb components separated	Minimal DOM updates in dumb components	Single reflow on data change	Low paint cost due to isolated updates	[OK] Good
Combined data fetching and UI rendering	Full component DOM updates	Multiple reflows on data fetch	Higher paint cost due to full re-render	[X] Bad

Rendering Pipeline

Smart components handle data and state changes, triggering updates only when necessary. Dumb components focus on rendering UI based on inputs, minimizing style recalculations and layout changes.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout due to unnecessary re-renders and data changes in UI components

Core Web Vital Affected

INP

This pattern affects rendering speed and interaction responsiveness by separating data handling from UI rendering.

Optimization Tips

1Keep data fetching and state management in smart components only.

2Use dumb components purely for rendering UI based on inputs.

3Avoid mixing data logic and UI to reduce re-renders and layout thrashing.

Performance Quiz - 3 Questions

What is the main performance benefit of separating smart and dumb components in Angular?

A Reduces unnecessary re-renders and improves input responsiveness

B Increases bundle size by duplicating code

C Triggers more layout recalculations

D Blocks rendering until data is fetched

DevTools: Performance

How to check: Record a performance profile while interacting with the component. Look for long scripting or layout tasks triggered by data fetching or UI updates.

What to look for: Check for fewer and shorter layout and paint events in the good pattern, indicating better responsiveness and less layout thrashing.

Practice

1. What is the main role of a smart component in Angular's smart and dumb component pattern?

easy

A. To handle user input events only

B. To only display data without logic

C. To manage data and business logic

D. To style the user interface

Solution

1. Step 1: Understand smart component responsibilities

   Smart components are designed to handle data fetching, state management, and business logic.

2. Step 2: Differentiate from dumb components

   Dumb components focus on displaying data and emitting events, not managing data or logic.

3. Final Answer:

   To manage data and business logic -> Option C

4. Quick Check:

   Smart component = data and logic [OK]

Hint: Smart components handle data and logic, dumb ones display only [OK]

Common Mistakes:

• Confusing dumb components as managing data
• Thinking smart components only display UI
• Assuming smart components handle styling only

2. Which of the following is the correct way to pass data from a smart component to a dumb component in Angular?

easy

A. Use a service to directly modify dumb component variables

B. @Output() data: any; in dumb component and bind in template

C. Use @ViewChild to access dumb component data

D. @Input() data: any; in dumb component and bind in template

Solution

1. Step 1: Identify data flow direction

   Data flows from smart to dumb components via inputs.

2. Step 2: Use Angular syntax for input binding

   Dumb components declare @Input() properties to receive data from parents.

3. Final Answer:

   @Input() data: any; -> Option D

4. Quick Check:

   Data to dumb = @Input() [OK]

Hint: Use @Input() to pass data down from smart to dumb [OK]

Common Mistakes:

• Using @Output() to pass data down instead of events up
• Trying to access dumb component data directly via ViewChild
• Modifying dumb component state via services without inputs

3. Given the following Angular code, what will be the output displayed by the dumb component?

/* Smart component template */
<app-dumb [title]="pageTitle" (clicked)="onClicked()"></app-dumb>

/* Smart component class */
pageTitle = 'Hello World';
onClicked() { console.log('Clicked!'); }

/* Dumb component template */
<h1>{{ title }}</h1>
<button (click)="clicked.emit()">Click Me</button>

/* Dumb component class */
@Input() title: string;
@Output() clicked = new EventEmitter<void>();

medium

A. Displays 'Hello World' and logs 'Clicked!' on button click

B. Displays nothing and logs 'Clicked!' on button click

C. Displays 'Hello World' but does not log anything

D. Throws an error because of missing @Output() decorator

Solution

1. Step 1: Analyze data binding from smart to dumb

   The smart component passes 'Hello World' via [title] input, so dumb displays it.

2. Step 2: Analyze event emission and handling

   The dumb component emits clicked event on button click, smart component listens and logs 'Clicked!'.

3. Final Answer:

   Displays 'Hello World' and logs 'Clicked!' on button click -> Option A

4. Quick Check:

   Input shows title, output triggers log [OK]

Hint: Input shows data, output triggers event handled by smart [OK]

Common Mistakes:

• Thinking dumb component logs directly
• Assuming missing decorators cause runtime error here
• Ignoring event binding from dumb to smart

4. Identify the error in this dumb component code that prevents it from emitting events to the smart component:

@Component({
  selector: 'app-dumb',
  template: `<button (click)="clicked.emit()">Click</button>`
})
export class DumbComponent {
  clicked = new EventEmitter<void>();
}

medium

A. EventEmitter should be imported from '@angular/core/testing'

B. Missing @Output() decorator on the clicked property

C. The template syntax for click event is incorrect

D. The clicked property should be a function, not EventEmitter

Solution

1. Step 1: Check event emitter declaration

   The clicked property must have @Output() decorator to emit events to parent.

2. Step 2: Verify imports and syntax

   EventEmitter is correctly imported from '@angular/core', template syntax is correct.

3. Final Answer:

   Missing @Output() decorator on the clicked property -> Option B

4. Quick Check:

   @Output() missing = no event emission [OK]

Hint: Always add @Output() to EventEmitter properties [OK]

Common Mistakes:

• Forgetting @Output() decorator
• Importing EventEmitter from wrong package
• Miswriting template event binding syntax

5. You want to refactor a large Angular component that mixes data fetching, logic, and UI display into smart and dumb components. Which approach best follows the smart and dumb component pattern?

hard

A. Create a smart component to fetch data and handle logic, pass data via @Input() to dumb components that only display UI and emit events

B. Move all logic and data fetching into dumb components and keep smart components only for styling

C. Combine smart and dumb components into one to reduce complexity

D. Use dumb components to fetch data and smart components to display UI

Solution

1. Step 1: Separate concerns by responsibility

   Smart components should handle data fetching and logic, dumb components focus on UI and user interaction.

2. Step 2: Use Angular bindings correctly

   Pass data from smart to dumb via @Input() and receive events via @Output().

3. Final Answer:

   Create a smart component to fetch data and handle logic, pass data via @Input() to dumb components that only display UI and emit events -> Option A

4. Quick Check:

   Smart = logic/data, Dumb = UI only [OK]

Hint: Smart handles data/logic; dumb handles UI and events [OK]

Common Mistakes:

• Putting logic in dumb components
• Merging smart and dumb components unnecessarily
• Reversing data flow direction