> The problems that GraphQL solves > 1. Mobile apps break periodically after API changes The author says that GraphQL solves this problem because GraphQL APIs

> The problems that GraphQL solves > 1. Mobile apps break periodically after API changes The author says that GraphQL solves this problem because GraphQL APIs never contain breaking changes (the author phrases it slightly differently). I disagree: breaking changes happen when you don't have proper diligence and review of changes. I've seen breaking changes happen in GraphQL and REST APIs, and they are always because people didn't consider how their changes would break the clients - it had nothing to do with the engine powering the API. I'm not strongly anti-GraphQL, but I don't believe that you will avoid breaking API changes just by adopting it. Granted, one might argue that my experience is with people who were "doing GraphQL wrong". Well, no disagreement there, but it reinforces my point that a protocol or language won't protect you from human error.