Compose Your Mobile App With GraphQL
summary
Claims that Jetpack Compose apps can drop view models by using a GraphQL normalized cache as the single source of truth, demonstrated with an experimental Apollo Kotlin Compose library and a Kotlin compiler plugin that collocates fragments in Kotlin files. Demo builds a GraphQLConf app using a useQuery composable and generated fragment types, persisting data in the cache so network calls and fake-service testing simplify. Works end-to-end in the demo though some ID ordering and IDE opt‑in (K2 front‑end IR registry key) issues remain; the repos are experimental but usable.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:59Mobile architecture pitfalls
- 10:26Simplify with GraphQL and Compose
- 12:37Apollo Kotlin Compose
- 14:23Live demo setup
- 17:19Conference app with Compose
- 21:25UI with fragments and composables
- 24:18Closing thoughts
- 25:01Questions and answers session
related talks
24mServer-Driven UI with Jetpack Compose and GraphQL
19mUsing Jetpack libraries in Compose
01h 00mJetpack Compose - Next Gen Kotlin UI Toolkit for Android
01h 12mJetpack Compose over inheritance
36mImplementing an Android client that brings out GraphQL’s strengths
47mUp to Date? Talking About Your App
45mFirst look at Jetpack Compose
45mOn the road to Jetpack Compose