// the take
Apollo Angular is the official Angular binding for Apollo Client: an injectable `Apollo` service plus HTTP/batch links and schematics that expose queries, mutations and subscriptions as RxJS Observables. It's for teams already on GraphQL who want Apollo's cache and devtools with Angular-native DI and `async` pipe ergonomics instead of hand-rolling an Apollo wrapper.
It's a thin layer over @apollo/client core, so you inherit Apollo's normalized cache, devtools extension, and optimistic UI support rather than a reimplementation that could drift from upstream behavior. The API fits Angular idioms well - injectable service, Observable-based `watchQuery`, clean with `async` pipe and `OnPush` change detection. `ng add apollo-angular` gives a real zero-config install via schematics, and persisted-queries/batch-HTTP-link are split into separate packages so you're not pulling in code you don't use. It's maintained by The Guild, who also own GraphQL Code Generator and other GraphQL tooling, so it's not an orphaned one-off wrapper.
Everything is RxJS-first - `map`/`pipe` on every query result - with no bridge to Angular signals, which is where Angular's own reactivity model has been heading since v16; that's two reactivity systems to reconcile in a modern app. You inherit Apollo Client's full cache-configuration complexity (type policies, field policies, normalization edge cases) with nothing here to soften that learning curve. The package has had a hard v1/v3 split tied to Apollo Client's own major versions, so upgrades on either side can force a coordinated bump. And because it's a wrapper, any bug or performance regression in @apollo/client itself passes straight through - you're exposed to upstream's release cadence, not just this repo's.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →