> On top of these, we built new tools and workflows for GraphQL developers. The new Apollo VS Code plugin puts valuable information about your schema — like the average latency of a specific field — right at your fingertips at development time.
This site is from creators of MeteorJS, the Meteor Development Group Inc.
Yup, all three are customers.
Despite that, I wish more time were invested in the OSS native apollo libraries (iOS, Android). There still isn't a way to do cache invalidations, and both libraries (perhaps understandably so) are well behind apollo-js in features. I would build something myself as a PR (and perhaps this is a problem with most GitHub projects), but non-trivial PRs seem to be left sitting for months or never touched at all by maintainers.
I bet the Apollo folks are just focusing their efforts where interest lies, but there really isn't a great, fully-featured OSS graphql client for mobile right now. React Native + apollo-js does not count to me: I have never used a React Native app I've felt acceptable on Android, and have only found marginally acceptable iOS apps in the wild.
The one thing that seems like a bit of a tough sell with this announcement is it looks like a lot of these integrations are pretty deeply intertwined with different parts of the framework and might not be easy to set up if you're using just the Apollo client and not the server. Just browsing quickly I see that some of the components require some workarounds and proxies and such with other backends. The post talks about making it easy to incrementally add graphql to existing apps, but for any apps built in languages other than NodeJS I'd worry that it might not be a first-class experience to use the entire platform.
I'll definitely have to look through the docs more thoroughly though, there's a lot here.