The client teams at Apollo GraphQL are committed to providing a welcoming, responsive, and helpful environment for GraphQL developers. Whether you’ve been an Apollo power user for years or hours, read on for some news and tips so you can get the most out of our community.
Where to get the help you need
The Apollo GraphOS Discord Server (new!)
Head on over to the Apollo GraphOS Discord server and say hello! All the Apollo client library maintainers are here, as are a growing number of Apollo developer community members. If you’re already a Discord user you can expect a familiar experience; we have forum channels for
backend questions plus regular live streams from Apollonauts (our name for Apollo employees). Apollo Client, Apollo iOS, and Apollo Kotlin users have already asked a ton of great questions in the
frontend channel. For more information about our Discord server, see this post!
Maintainer Office Hours (new!)
One of the biggest reasons we’re excited about the Discord server is our new Maintainer Office Hours series, where our open-source client maintainers will regularly stream to answer community questions live on video. These sessions will be recorded and shared afterwards as well!
The Apollo GraphQL Forums
In addition to Discord, we also have a community forum powered by Discourse. All the client maintainers monitor this forum directly so whether you’re there or on Discord, expect the same level of helpfulness and support from Apollonauts and community members alike.
Choosing the right place to post
For any Apollo Client (web) feature request, please post an Issue in the Apollo Feature Requests repo on GitHub. Feature requests for Apollo Kotlin, Apollo iOS, and other Apollo projects should be opened as an Issue in their respective repos. To avoid duplicates, don’t forget to search existing Issues first!
Questions, advice, bugs, and how-to
For general questions, advice, how-to questions, or to figure out whether a certain behavior is a bug, consider posting in our Discord server (
frontend channel) or forum. For bug reports that are reproducible and actionable, post an Issue in the relevant client library’s repo.
Apollo Client, Apollo iOS, and Apollo Kotlin each have a
ROADMAP.md document in their project root. For a high-level overview of what’s coming and approximate dates, please take a look! We’re really excited about the future and would welcome your feedback on our plans. If you think our roadmap should include a feature that you care about, see the “Feature requests” heading above.
If you’re interested in contributing code to our open-source projects, we’d be eager to review your work! For small documentation adjustments, feel free to open a PR right away. For larger changes, we strongly recommend opening an Issue first with plenty of detail. That will give the maintainers an opportunity to share feedback and guidance before you start implementing. For further guidance, see the
CONTRIBUTING.md document in the Apollo Client, Apollo iOS, or Apollo Kotlin repo.
How to get the most out of the Apollo community
If you’re in search of answers to questions or think you may have found a bug, we’re here to help! Apollonauts are committed to responding quickly and helpfully to community members and no question is too small or too big. In order to get the most value possible out of our community, here’s some advice.
Chances are your question is not unique. Taking a few moments to search the Issues of Apollo Client, Apollo iOS, or Apollo Kotlin might pay off. Also try searching the Apollo GraphQL Forums and the Apollo GraphOS Discord for context.
Figure out what you need
Are you looking for open-ended, opinionated advice about a broad concept or topic? Do you need a discrete answer to a specific question? Action on a potential bug? Sharing a feature request? Knowing the desired outcome will help you figure out what a community member or client maintainer might need in order to resolve your inquiry.
Share as many details as possible
I’d like to share of one of my favorite quotes:
That’s the answer you’re likely to get unless you share plenty of information. Inquiries that are only a few sentences long without accompanying sample code are almost always too vague to resolve effectively. The gold standard is to prepare a runnable reproduction that demonstrates the problem. A runnable reproduction has two key aspects: (1) it’s a simple application that can be installed and run within a few moments and (2) it clearly demonstrates the problem or question to be resolved. This may seem burdensome at first but it’s the best way to get a helpful response in a relatively short amount of time. The less time community members and maintainers need to spend asking clarifying questions, the more time they have to assist you!
If you’re not sure where to begin, we have a few templates that you can use:
react-apollo-error-template(Apollo Client, React): Minimal bug reproduction app with no backend dependencies
rn-apollo-client-testbed(Apollo Client, React Native, Expo): Minimal React Native app using Expo with debug and profiling functionality
spotify-showcase(Apollo Client, React, Apollo Server): Full-stack Spotify clone powered by Apollo Client + Apollo Server. Not designed as a bug reproduction template but can be used as such if you want to demonstrate an issue in a fairly complex app
next-apollo-example(Apollo Client, Next.js): Similar to
react-apollo-error-templatebut for Next.js reproductions instead of vanilla React
apollo-kotlin-tutorial(Apollo Kotlin): Some Apollo Kotlin community members have cloned and modified our tutorial in order to show us how to reproduce bugs
- Confetti (Apollo Kotlin, Kotlin Multiplatform): This is an open-source KMM app that’s available in the Play Store for Android users and the App Store for iOS users. It’s probably not ideal for bug reproductions but for higher-level discussions about architecture or API design it could be useful. Note: one of the Confetti maintainers is an Apollonaut but Confetti itself is not affiliated with Apollo GraphQL.
Apollo Client (web) users can also consider sharing a Replay.io recording with us. Please make sure to create that recording from a development environment and make sure that it doesn’t contain any sensitive information you might not want to share.
If for some reason you are not able to share something runnable, please do include as many code samples and as much context as possible. It’s not as concrete as a runnable reproduction but can still help reduce the amount of time the community needs in order to fully understand the inquiry to the point where they can provide a helpful response.
Follow our Code of Conduct
If you haven’t read our Code of Conduct lately, please do so! This applies to any space run by Apollo, including our GitHub repositories, the Apollo GraphOS Discord, the Apollo GraphQL Forum. The Code of Conduct reflects our commitment to making the Apollo GraphQL Community a welcoming and safe space in which individuals can interact.
Let us know what you think
We want to make you successful! If you have any suggestions for our community please do contact email@example.com or reach out to an Apollonaut in one of our various channels. We would be very happy to hear from you!
Stay in our orbit!
Become an Apollo insider and get first access to new features, best practices, and community events. Oh, and no junk mail. Ever.
Make this article better!
Was this post helpful? Have suggestions? Consider so we can improve it for future readers ✨.