Isograph — Rethink GraphQL Powered React Apps
summary
Isograph proposes replacing fragment plumbing with a compiler that turns front-end resolvers into server queries, letting resolver fields act like callable UI pieces. The demo app Petless 3000 fetches data via useLazyReference/read, suspends on missing data, and updates with a generated mutation that refetches exactly the currently selected pet fields. Work-in-progress status means Typescript typing gaps, missing editor tooling and bundler integrations, but the prototype runs and suspension, refetching and component-as-field behavior all work.
AI-written summary · about
chapters (13)
- 0:00Introduction to Isograph
- 1:36The Problem with Boilerplate
- 2:50Analyzing GraphQL Workflows
- 5:04The Importance of Data Masking
- 7:31The Ideal Developer Experience
- 9:19Resolvers as Missing Primitive
- 11:05Resolver Components in React
- 13:50Fetching and Data Flow
- 15:26Advantages of Resolvers
- 18:55Tooling and Future Potential
- 20:20Live Demo and Implementation
- 26:56Roadmap and Community Call
- 28:21Q&A Session
related talks
33mPerforming Impossible Feats with Isograph
33mPerforming Impossible Feats with Isograph
30mGraphQL in the Era of React Server Components
26mAngular + GraphQL. We do it because we can!
32mFrom learning to thinking in GraphQL
23mA glimpse of GraphQL" Frontend developers’ life is easy now!"
26mIncrementally Adopting GraphQL. The Holy Grail?
24mBuilding Reactive GraphQL Apps With Apollo