Android client implementation that brings out the best of GraphQL

GraphQL is gathering the attention of many developers due to the expressive power of its API schema and the flexibility of its data acquisition. However, you may not be able to get the full benefit of GraphQL by simply integrating GraphQL into the architecture of an existing Android application. It would reduce development efficiency if you declared UseCase and/or Repository classes that do not match the actual processing or made mistakes in the GraphQL Fragment Colocation: the partition granularity, the file locations, etc. To bring out the best of GraphQL, it is essential to design an architecture that takes advantage of its characteristics and to utilize declarative UI. In this session, we will introduce ADR (Architecture Decision Records) accumulated through 2 years of operating a new product that fully adopted GraphQL. We use Apollo-Kotlin as our GraphQL client library. The topics will be as follows: - GraphQL and schema-driven development - Layered architecture actualized by the Apollo client - Jetpack Compose and GraphQL Fragment Colocation Let's understand the characteristics of GraphQL and learn how to accelerate schema-driven development. (Translated by the DroidKaigi Committee)