OnPush Strategy — Complete Guide

Introduction

OnPush Strategy — Complete Guide is essential for frontend developers and architects building AngularVerse Enterprise Angular Platform — Toolliyo's 100-article Angular master path covering CLI setup, standalone components, routing, reactive forms, HttpClient, RxJS, Signals, NgRx, Material, SSR, module federation, testing, and enterprise AngularVerse projects. Every article includes architecture diagrams, data-flow patterns, performance tactics, and minimum 2 ultra-detailed enterprise frontend examples (banking dashboard, ERP portal, SaaS admin, AI analytics UI, healthcare portal, micro frontends).

In Indian IT and product companies (TCS, Infosys, HDFC, Flipkart), interviewers expect onpush strategy with real dashboards, lazy-loaded modules, OnPush optimization, and measurable Web Vitals — not toy hello-world components. This article delivers two mandatory enterprise examples on Micro Frontend.

After this article you will

• Explain OnPush Strategy in plain English and in Angular / TypeScript architecture terms
• Apply onpush strategy inside AngularVerse Enterprise Angular Platform (Micro Frontend)
• Compare jQuery-style DOM hacks vs AngularVerse component-based, OnPush, and Lighthouse-monitored patterns
• Answer fresher, mid-level, and senior Angular, Signals, NgRx, and frontend architect interview questions confidently
• Connect this lesson to Article 65 and the 100-article Angular roadmap

Prerequisites

• Software: Angular 19+, VS Code and Angular CLI
• Knowledge: Basic TypeScript and HTML
• Previous: Article 63 — Responsive Layouts — Complete Guide
• Time: 28 min reading + 30–45 min hands-on

Concept deep-dive

Level 1 — Analogy

Change detection is a room inspection — OnPush only checks components when inputs or signals change, saving CPU on big trees.

Level 2 — Technical

OnPush Strategy powers enterprise frontends in AngularVerse: standalone components, lazy routes, typed forms, secure HttpClient, and Lighthouse-monitored bundles. AngularVerse implements Micro Frontend with production-grade scalability patterns.

Level 3 — Change detection & data flow

[Browser / Angular App]
       ▼
[Router → Components → Services]
       ▼
[Signals/RxJS → Change Detection]
       ▼
[OnPush / trackBy / Lazy Loading]
       ▼
[Lighthouse · Angular DevTools · CI/CD]

Project structure

AngularVerse/
├── src/app/features/   ← Lazy-loaded feature areas
├── src/app/shared/     ← Reusable UI components & pipes
├── src/app/core/       ← Guards, interceptors, singleton services
├── src/app/state/      ← Signals or NgRx (when needed)
├── src/assets/         ← Static assets and themes
└── e2e/                ← Cypress/Playwright quality gates

Hands-on implementation — Micro Frontend

Implement OnPush Strategy as a standalone Angular component for Micro Frontend: wire template, service, and routing; verify with ng serve and Angular DevTools.

1. Generate or open a standalone component with ng generate.
2. Define template, inputs, and inject services via inject().
3. Use async pipe or takeUntilDestroyed for subscriptions.
4. Run ng serve and verify in Angular DevTools.
5. Add a Jasmine spec with TestBed for critical behavior.

Anti-pattern (leaky subscriptions, no trackBy, default CD everywhere)

// ❌ BAD — default CD + no trackBy + memory leak
@Component({ template: '<div *ngFor="let item of items">{{ item.name }}</div>' })
export class BadListComponent implements OnInit {
  ngOnInit() { this.api.getItems().subscribe(items => this.items = items); }
}

Production-style Angular component

// ✅ PRODUCTION — OnPush Strategy on AngularVerse (Micro Frontend)
@Component({
  changeDetection: ChangeDetectionStrategy.OnPush,
  template: '@for (item of items(); track item.id) { <app-row [item]="item" /> }'
})
export class GoodListComponent {
  items = signal([] as Item[]);
  constructor(private api: ItemService, private destroyRef: DestroyRef) {
    this.api.getItems().pipe(takeUntilDestroyed(this.destroyRef)).subscribe(list => this.items.set(list));
  }
}

Complete example

@for (item of items(); track item.id) { <app-row [item]="item" /> }

The problem before Angular — OnPush Strategy

jQuery spaghetti and untyped vanilla JS do not scale to enterprise SPAs. AngularVerse replaces chaos with components, TypeScript, DI, and structured state.

• ❌ Global DOM manipulation — untestable, memory-leak prone
• ❌ No routing — full page reloads kill UX
• ❌ Ad-hoc state in window variables — impossible to debug at scale
• ❌ No lazy loading — 5MB initial bundle on mobile

AngularVerse applies components, routing, Signals/NgRx, and performance patterns from day one.

Frontend architecture

OnPush Strategy in AngularVerse module Micro Frontend — category: PERFORMANCE.

Material, OnPush, trackBy, defer, SSR, hydration, bundle tuning.

[Browser / Mobile]
       ↓
[Angular Bootstrap → Router]
       ↓
[Components / Services / Signals]
       ↓
[HttpClient → ASP.NET Core API]
       ↓
[Lighthouse · Bundle Analyzer · Cypress]

Change detection & data flow

Real-world example 1 — SSR + Hydration for SEO Catalog

Domain: E-Commerce / SEO. Product pages must be indexed by Google. AngularVerse uses Angular SSR with hydration and deferrable views for reviews section.

Architecture

@angular/ssr with Express server
  provideClientHydration() in app config
  @defer (on viewport) for reviews component
  prerender top 1000 product routes

Angular / TypeScript

bootstrapApplication(AppComponent, {
  providers: [provideClientHydration(), provideRouter(routes)]
});

// template
@defer (on viewport) {
  <app-product-reviews [productId]="id" />
}

Outcome: Google indexed 98% product pages; TTFB 180ms on SSR.

Real-world example 2 — AI Analytics Dashboard with Signals

Domain: AI / Analytics. KPI cards and charts must react to filter changes without RxJS boilerplate. AngularVerse uses computed signals derived from filter signal.

Architecture

filterSignal = signal({ region: 'IN', range: 30 })
  kpis = computed(() => calcKpis(filterSignal(), data()))
  Chart.js via ng2-charts standalone wrapper
  defer block for heavy chart bundle

Angular / TypeScript

readonly filter = signal({ region: 'IN', days: 30 });
readonly revenue = computed(() =>
  this.analyticsService.sumRevenue(this.filter(), this.rawData())
);

Outcome: Filter-to-chart update 16ms; bundle split saves 180KB on landing.

Angular architect tips

• Prefer standalone components and lazy routes in new AngularVerse features
• Use Signals for local UI state; NgRx when multiple features share complex state
• Always unsubscribe or use async pipe / takeUntilDestroyed
• Measure with Lighthouse and webpack-bundle-analyzer before every release

When not to use this Angular pattern for OnPush Strategy

• 🔴 Static marketing page with no interactivity — plain HTML may suffice
• 🔴 NgRx for a 3-component app — Signals or a service is enough
• 🔴 Default change detection on huge lists — use OnPush + trackBy
• 🔴 Micro frontends before modular monolith proves team boundaries

Testing & validation

import { ComponentFixture, TestBed } from '@angular/core/testing';
import { OnPushStrategyComponent } from './onpushstrategy.component';

describe('OnPushStrategyComponent', () => {
  let fixture: ComponentFixture<OnPushStrategyComponent>;
  beforeEach(async () => {
    await TestBed.configureTestingModule({
      imports: [OnPushStrategyComponent]
    }).compileComponents();
    fixture = TestBed.createComponent(OnPushStrategyComponent);
    fixture.detectChanges();
  });
  it('should create', () => {
    expect(fixture.componentInstance).toBeTruthy();
  });
});

Pattern recognition

Large list → OnPush + trackBy. Shared state → Signals/NgRx. Heavy routes → lazy load. Live updates → SignalR/WebSocket. Slow render → profile in Angular DevTools.

Common errors & fixes

• Subscribing without cleanup — Use async pipe or takeUntilDestroyed(this.destroyRef).
• Missing track in @for / ngFor — Use track item.id and OnPush on large lists.
• Default change detection on huge trees — Use OnPush, signals, and lazy-loaded routes.

Best practices

• 🟢 Use takeUntilDestroyed or async pipe for subscriptions
• 🟢 Use OnPush, trackBy, and lazy loading on large apps
• 🟡 Enable Lighthouse budgets on every production build
• 🟡 Run bundle analyzer after adding dependencies
• 🔴 Never render huge lists without trackBy and virtualization
• 🔴 Never deploy without unit + e2e + lint checks in CI

Interview questions

Fresher level

Q1: Explain OnPush Strategy in an Angular interview.
A: Cover component design, DI, change detection strategy, and one real project where you measured performance or fixed a bug.

Q2: Signals vs RxJS — when to use each?
A: Signals for local UI state and computed values; RxJS for async streams, HTTP, and complex event composition.

Q3: What is Angular change detection?
A: Angular walks the component tree checking bindings — Default checks broadly; OnPush checks when inputs/signals/events change.

Mid / senior level

Q4: How do you find and fix a slow Angular screen?
A: Angular DevTools profiler + Lighthouse → find heavy components → OnPush, track in @for, lazy routes, defer blocks.

Q5: How do you prevent memory leaks in Angular?
A: Use async pipe or takeUntilDestroyed; avoid manual subscribe without cleanup in components.

Q6: How do you secure Angular apps?
A: DomSanitizer for HTML, CSRF tokens, HttpOnly cookies for tokens, route guards, CSP headers, and trusted API origins.

Coding round

Write Angular TypeScript for OnPush Strategy in AngularVerse Micro Frontend: show component/service code, routing notes, and test assertions.

@Component({
  standalone: true,
  changeDetection: ChangeDetectionStrategy.OnPush,
  template: '@for (item of items(); track item.id) { <app-row [item]="item" /> }'
})
export class OnPushStrategyComponent {
  items = signal<Item[]>([]);
}

Summary & next steps

• Article 64: OnPush Strategy — Complete Guide
• Module: Module 7: UI & Performance · Level: ADVANCED
• Applied to AngularVerse — Micro Frontend

Previous: Responsive Layouts — Complete Guide
Next: TrackBy — Complete Guide

Practice: Run today's code with ng serve and verify in Lighthouse — commit with feat(angular): article-64.

FAQ