Our ongoing journey from REST to GraphQL on Android
summary
Company migrates REST to GraphQL for Android using AWS AppSync backend and the Apollo Kotlin multiplatform SDK, relying on Apollo codegen, coroutines and Flow. Subscriptions power real‑time SMS/MMS; nested queries once produce 7–10s responses until backend adds a lastMessage field and optimizes resolvers. A custom websocket token refresh is implemented and upstreamed to Apollo. CI jobs fetch schemas per environment (GitLab daily PRs), monitoring uses Chucker and clients initialize Apollo lazily via Dagger.
AI-written summary · about
chapters (21)
- 0:00Introduction and journey overview
- 1:05Why choose GraphQL
- 3:35GraphQL benefits and use cases
- 5:20Migration strategy from REST
- 7:29Backend setup with AppSync
- 8:33Android client with Apollo SDK
- 11:23Setting up GraphQL in Android
- 17:32Lessons learned from migration
- 21:48Cross-team collaboration tips
- 23:17Android-specific optimizations
- 24:25Monitoring GraphQL requests
- 26:09Demo of monitoring tool
- 28:00Nested queries and performance
- 31:17Handling GraphQL subscriptions
- 34:58Contributing to Apollo SDK
- 37:06Error handling in GraphQL
- 40:39Automating schema updates
- 43:08Apollo community and resources
- 44:12Key takeaways from migration
- 47:05Q&A on security and versioning
- 50:21Q&A on monolith splitting
related talks
45mOur ongoing journey from REST to GraphQL on Android
39mOur ongoing journey from REST to GraphQL on Android
41mOur ongoing journey from REST to GraphQL on Android
29mMigrating to GraphQL on Android with Apollo
37mGraphQL on Android is here!
36mImplementing an Android client that brings out GraphQL’s strengths
54mTake Control Of Your APIs With GraphQL
38mAPI Modernization with GraphQL