> - good for frontend I'm not even sure about this part. I worked on a project recently where the mobile front end team hated working with GraphQL. They were

> - good for frontend I'm not even sure about this part. I worked on a project recently where the mobile front end team hated working with GraphQL. They were far more used to working with REST/HTTP APIs, and in this particular project they only communicated with a single backend. The team saw it as extra layers of complexity for no benefit. The GraphQL backend was responsible for pulling together data from several upstream systems and providing it to clients. But the architect never was able to convince me of a single benefit here compared to REST.