Morning all. Can someone share how your developers experience look like in term of schema downloading? I am interested in where do you download the schema (Apollo Studio, your servers or something else), at what point of the dev lifecycle schema is uploaded, and when and by whom it is downloaded. Anything you can share regards how useful it is greatly appreciated. I am trying to figure out what would be the smoothest process for us, taking into account that this step never existed before.

We have a separate repository with a daily github action that downloads the schema (it also has queries shared between the mobile apps), and if the schema is different than the current one the action creates a pull request + pings relevant people. This repository is then used as a submodule in the apps that use the queries. I think it works well, other than the general downsides of using git submodules

Interesting. Thanks for sharing.

Hey, I am using this plugin to AS and i have a config file with different environment schemas and I let it download the schema on demand (whenever our BE team sends a memo that there's something new). But I'm pretty new to GraphQl so I'm not sure if this will suite us well to the future

Small team (3 developers) so changes are known instantly. Generally I work on or am informed by another developer of upcoming changes. In our production and staging build types (4 in total release vs debuggable variants) we run

ApolloDownloadSchemaTask

with a passed in endpoint (one of our servers) that differs per variant. It works well for now but if we were to grow larger something else may suit better.

Thank you @david.bilik and @maxgdn for your stories.