[moomoo11]

When you have multiple consumers who need different shapes of the same data, like mobile clients or external consumers.

We used it at $lastJob and I thought it was a lot of complexity for what it offered. I had done a analysis of our gql stuff and maybe 20% of the time consumers took advantage of it.

Personally I'd just build a good RESTful API and not cram shit into responses that makes no sense. It isn't that hard to batch requests together, and imo I'd opt for KISS 100 out of 100 times.

I haven't worked somewhere that took 80%+ advantage of gql. Maybe its only Meta and a handful other capable places that really need gql, IMO.