Jeff Auriemma at LeadDev West Coast 2023
summary
Claims that GraphQL turns APIs into self‑documenting, designer‑friendly surfaces and makes experiments fast: the introspection ability plus a GraphQL IDE lets designers query live fields; the combination of ID + __typename enables a normalized cache so clients avoid redundant network requests; built‑in directives like @include and @deprecated let teams run and clean up A/B tests. Outcome reported: product iterations shrink from months to weeks and designers self‑serve constraints without engineering bottlenecks.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:42GraphQL core concepts
- 1:46GraphQL vs REST basics
- 2:50GraphQL for designers
- 4:14GraphQL introspection
- 5:16REST API limitations
- 6:40REST nested data challenges
- 7:44GraphQL product iteration
- 8:26Normalized data with ID
- 9:27GraphQL caching benefits
- 9:49GraphQL A/B testing
- 10:31Flexible product experiments
- 10:53Summary
related talks
23mA glimpse of GraphQL" Frontend developers’ life is easy now!"
19mGraphQL: Accelerating Digital Transformation Through Modern APIs.
25mAI, GraphQL, and the Rise of Malleable Applications
30mGraphQL Is a Superpower for Your Product Manager and Designer
25mThe Intersection of GraphQL & Design Systems in Product Dev.
29mWrite Queries, Not Code
30mWhy GraphQL vs. Why not GraphQL
12mWhy GraphQL?