Disagree - GraphQL is a legit better way to build APIs. As a backend engineer, I publish a schema of all the available data - the frontend can fetch it in any

Disagree - GraphQL is a legit better way to build APIs. As a backend engineer, I publish a schema of all the available data - the frontend can fetch it in any shape it prefers. Web UIs and mobile UIs often have different views, so they want different data, and fetching it in one request or many is up to the preference of the UI. I don't have to build different REST endpoints presenting some data in a different shape for performance reasons or because different applications wanted to request the data in a different way. As a frontend engineer, all the data is often already there unless I'm building some new feature the backend doesn't understand yet. I'm free to refactor my application without bothering changing the REST API - and GraphIQL lets me inspect the api and mock queries for how I might fetch the data for a given view. It's a cleaner contract to let different people get their job done with less fuss - game changer.