I think it exposes a better more consistent contract between the frontend and backend, but I might not use it if my product were an api - it's harder for users

I think it exposes a better more consistent contract between the frontend and backend, but I might not use it if my product were an api - it's harder for users who are used to traditional rest apis to consume. I like how as a backend engineer you can just publish all the data that makes sense in the graphql schema and the frontend folks can just grab whatever they want in a single request to populate whatever view they're working on - easy to explore with graphiql, and you can introspect the schema to generate types for typescript...