Our ongoing journey from REST to GraphQL on Android
summary
Migration moves Heroku from REST to a GraphQL API built on AWS AppSync with the Android client using Apollo Kotlin, separate OkHttp clients, Dagger Hilt lazy injection and Chuck for request inspection. Nested queries originally cause 7–10 seconds responses until backend SQL/index changes or schema fields (e.g. lastMessage) are added. Subscriptions require custom token/ reconnect handling — a contributed Apollo fix — and error handling is fragmented, so CI-driven schema automation and close backend collaboration are critical.
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 1:11What is GraphQL
- 3:17Why migrate to GraphQL
- 5:03Underlying technologies
- 7:29Setting up Apollo Kotlin
- 15:25Lessons learned from migration
- 22:51Nested queries and performance
- 25:38Challenges with subscriptions
- 31:36Error handling differences
- 33:47Schema automation in CI
- 37:21Key takeaways and conclusion
related talks
41mOur ongoing journey from REST to GraphQL on Android
45mOur ongoing journey from REST to GraphQL on Android
52mOur ongoing journey from REST to GraphQL on Android
29mMigrating to GraphQL on Android with Apollo
54mTake Control Of Your APIs With GraphQL
37mGraphQL on Android is here!
36mImplementing an Android client that brings out GraphQL’s strengths
43mExploring GraphQL on Android