> I don't think necessarily GraphQL is hard to understand as a concept It was surprising to us as well! But working with lots of users who are new to GraphQL,

> I don't think necessarily GraphQL is hard to understand as a concept It was surprising to us as well! But working with lots of users who are new to GraphQL, there are a few speed bumps along the way before you get to "implementing GraphQL in production." You have to convince your GraphQL users that: 1. It won't take too long to understand 2. It will be worth the effort Anything you can do to make building a valid GraphQL query (both syntactically and semantically) faster helps with #1, and will get your users further along. Making it so that users can see success/data flowing in as quickly as possible helps with #2. From there, like you mentioned, there are lots of additional challenges, but for this post we're focusing on getting new users over the most initial hurdles.