GraphQL for mobile developers
summary
GraphQL is useful for iOS when paired with Apollo client and a Django/Graphene backend: one endpoint serves precise queries, shrinking a film-list payload from ~18.8 KB to ~2.0 KB in the demo. The workflow uses the introspection schema to generate API.swift and speeds development (one and a half backend devs moved faster). Watch for hazards: base64 ID issue requiring decode, missing subscription support, Apollo cache defaulting to cached data, and offline complexity that led to a separate Realm sync.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:24ABOUT ME
- 1:14INTRODUCTION
- 1:46WHAT IS IT?
- 3:03THIS IS ALL GOING TO GO A BIT...
- 3:40EXAMPLE - STAR WARS IMDB
- 5:28WHAT JUST HAPPENED?
- 5:40HOW DO WE DO THIS ON IOS?
- 8:04ADDING A NEW SCREEN TO STAR WARS IMDB
- 8:31CREATING A NEW QUERY
- 12:43IN ACTION..
- 13:16THE REST ALTERNATIVE
- 14:43MUTATING DATA
- 15:17HANDLING ERRORS
- 16:13WHAT WE'VE COVERED SO FAR...
- 16:35CASE STUDY
- 17:14PITFALL O: UPDATES
- 18:02IDs
- 20:01SUBSCRIPTIONS
- 20:54THE CACHE • Apollo has fancy caching
- 22:16OFFLINE
- 23:30OTHER PITFALLS
- 25:25CONCLUSION
- 25:43SHOULD YOU USE GraphQL?
- 27:06FURTHER READING
- 27:42QUESTIONS?
related talks
29mBuilding better mobile apps with GraphQL
24mBuilding native mobile apps with GraphQL
51mImproving the architecture of your iOS app with GraphQL
35mGraphQL in real life
41mStrong typing from the server to the UI with GraphQL
47mGraphQL: How to Persuade the Server to Fit the App
37mGraphQL on Android is here!
01h 00mGraphQL - A query language to empower your API consumers
