Guess it depends on use case. When it's not very clear what your client wants to consume and your product is evolving rapidly, HTTP APIs tend to turn into a mes

Guess it depends on use case. When it's not very clear what your client wants to consume and your product is evolving rapidly, HTTP APIs tend to turn into a mess and lead to a gigantic amount of requests just to start the app (which, to be fair, is less of a problem now with HTTP/3). GraphQL has allowed my company to keep our network traffic very lean while evolving a product very quickly and to have very few issues in communicating between our mobile application and backend teams. But once again, I can see how our requirements are not everyone else's.