Yesterday we launched a new landingpage and a sign-up form to give users early access to the new GraphQL API. This is a big step forward for Comfortable, not only because GraphQL was on the roadmap since we started the project, but we are very pleased with the outcome and believe this will make the project fundamentally better. It's great to be finally able to show it to a broader audience.

As soon as we've made first contact with GraphQL in early 2017, Christian and I quickly understood its potential and how great it would work out when used with a Headless CMS. However, it took us some time to get GraphQL implemented, since we had a lot of work to do to build the Beta version of the new SaaS Version of Comfortable (yes, there is an older non-SaaS version from 2015). We were, and still are, a team of just two developers working part-time on Comfortable and additionally doing project based work. That makes it quite demanding to ship new (especially large) features at the same speed as a larger company with a dedicated team of engineers. Also, it was also not a top-priority feature at the beginning and therefore staged for the end of 2018. We were not so sure in the beginning how big GraphQL would grow in early/mid 2017 – it became clear quite quickly that there was no reason for such questioning. Quite hilarious when I think about it today.

In the meantime, while be were busy working on the beta of Comfortable, a lot of new headless CMS launched. Funded by VC money and either with GraphQL support or even entirely based on GraphQL. We took this as confirmation for what we thought at the early beginning about GraphQL. I can't say that I'm not a bit sad that we prioritized this feature sooner. Even well established products like Contentful and Prismic now provide a GraphQL API. Although GraphQL is not a new fancy thing anymore for headless CMS we're still proud of the way we've implemented it in Comfortable and happy how well it plays out. I'm very curious to see what people are going to do with it.

Users will be granted access to the new API in batches – the reason is that we still need to validate some things like performance when the workload increases and to able to deal better with bugs. However, the goal is to make GraphQL available for everyone as soon as possible.