GraphQLifying React Native App
summary
Migration of a 200k+ weekly‑user React Native app to Apollo Client 3.0 and a new GraphQL backend cuts the startup surface from 15 API calls down to one (plus one registration mutation) by using a GraphQL gateway (Apollo Server 3 POC, GraphQL Java in production), client‑side fetch for optimized articles via local resolvers + axios with a schema‑enforcement layer, cache tweaks with typePolicies/keyFields and reactive variables for local state; pitfalls: local resolvers are deprecated, reactive vars need manual persistence, and cache persistence required workarounds.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:31Proof of concept with Apollo
- 10:34Backend solution and local resolvers
- 14:25Type policies and Apollo cache
- 16:31Reactive variables for local state
- 22:08Debugging and testing with Apollo
- 25:57Outcome and lessons learned
related talks
33mMigrating from redux to Apollo
23mA glimpse of GraphQL" Frontend developers’ life is easy now!"
27mReact State Management In a GraphQL Era
24mBuilding Reactive GraphQL Apps With Apollo
52mState management in a GraphQL era
24mModern Apollo Client React
45mOur ongoing journey from REST to GraphQL on Android
23mGraphQL State Management for React Native