I have no idea what Apollo Graph QL is, but it was interesting to search by URL and see the progression of related HN titles and their engagement. 2018 July. Apollo server 2 released woo! (mostly ignored) 2019 Feb. We switched away from Slack woo! . . . (Some PRs everybody ignored) 2019 June. We got a $22M investment woo! . . . (Many PRs everybody ignored) 2022 Dec. Oops, we are laying of lots of people...
Apollo is synonymous with Graphql at this point. If you need you consume a Graphql API you most certainly reach out for Apollo on the clientside to query data.
Over the last couple of weeks I’ve been assessing whether to use Apollo in a Swift iOS application. If your backend is using GraphQL then it’s almost impossible to find even a StackOverflow answer from anyone not using Apollo.
But when I tried it out, I found the package was cumbersome to use, and the generated code was over-dimensioned and inelegant, and the dependency itself pulled in other dependencies.
With bitter experience of using other packages in the past, which start out as helpful, but which end up a burden to the codebase, I decided to write some queries and mutations by hand. And it was super-simple.