§ 04 · Domain mastery

Angular Engineering

Enterprise Angular that lasts a decade — design system, NgRx, MFEs, a11y welded in.

Angular built like furniture — square, joinery visible, tested. Shared design system with tokens and theming, disciplined NgRx state, micro-frontend seams that don't leak, and WCAG audited rather than claimed. We modernize legacy AngularJS estates without a rewrite when the accounting still works.

Talk to a partner →All services
§ I

Pillars

01

Design system with real tokens

Themed at the token layer, not per-component overrides. Storybook is the single source of truth; the app is downstream.

02

NgRx state, disciplined

Feature-scoped stores, effects that don't leak side effects, selectors as the API. No 'shared' god-store that becomes untestable in year two.

03

Micro-frontend seams

Module federation across teams, contracts at the edge, versioned shared libraries. Independent deploys without accidental global state.

04

WCAG 2.2 AA — audited

Keyboard-first navigation, focus management, ARIA where it actually helps. Automated in CI plus periodic manual audits — not a checkbox.

05

Standalone components + Signals

Modern Angular that shed the NgModule ceremony, with Signals-based state for local reactivity. Migrations planned, not accidental.

06

Legacy AngularJS bridging

Downgrade/upgrade patterns and incremental migration when the estate is too big to rewrite. Ship value on Monday; still on Angular in six years.

§ II

Domain vocabulary

The words that separate insiders from readers.

Standalone componentThe post-NgModule world. Teams still saying 'add it to the module' are on an old mental model.
SignalAngular's fine-grained reactivity primitive. Where the framework is heading; RxJS isn't going away, but Signals change how you compose UI state.
Change detection strategyOnPush vs Default. Everyone knows the words; few teams actually enforce OnPush and reap the perf wins.
Effect (NgRx)The place async side effects belong. Effects that call other effects are a well-known code smell insiders name on sight.
Module federationRuntime composition of independently deployed frontends. Different from build-time monorepo splitting; teams conflate the two.
Zone.jsAngular's change-detection auto-trigger. Zoneless is coming — knowing why matters more than opting in on day one.
Angular ElementsAngular components exposed as Web Components. The escape hatch for gradual adoption inside a non-Angular host.
Nx affectedOnly rebuild/test what a change actually touched. Teams that skip it hit 40-minute CI on 200-package monorepos.
§ III

Open problems we help with

§ IV

What we ship

  1. 01A design system in Storybook, themed at the token layer.
  2. 02An NgRx layout your team can navigate a year from now.
  3. 03A micro-frontend host with a signed shared-library contract.
  4. 04A CI a11y gate plus a scheduled manual audit.
  5. 05A migration plan from AngularJS or older Angular that ships value on the way.
  6. 06A handover: the docs, the tests, the on-call runbook.
NEXT STEP
How does this look in your case?
Talk to a partner →
Season