Building better mobile apps with GraphQL
summary
Explains why GraphQL began at Facebook in 2012 to power native mobile apps and shows concrete tooling and results: GraphiQL autocompletion and live examples, an iOS Swift client with Swift codegen with compile-time types, Apollo tooling including a 14‑day trial and a subscriptions transport, and a server model as a thin resolver layer that combines data sources. Claims include backwards compatibility (Facebook supports hundreds of app versions still supported), and field-level visibility via field-level performance metrics so migration impact is measurable.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:53ReactiveConf 2016
- 2:57GraphQL pain points
- 7:55GraphQL for product developers
- 14:09GraphQL servers
- 18:24GraphQL as an ecosystem
- 19:10Product developers
- 19:59Continuous evolution
- 22:27Questions
related talks
24mBuilding native mobile apps with GraphQL
27mExploring GraphQL
41mStrong typing from the server to the UI with GraphQL
51mImproving the architecture of your iOS app with GraphQL
11mA Brief History of GraphQL
28mGraphQL for mobile developers
40mGraphQL: Designing a Data Language
01h 00mGraphQL - A query language to empower your API consumers
