Show HN: How to visualize your GraphQL schema?
blog.graphqleditor.com
blog.graphqleditor.com
My concern is around monetization. Most devs only author schemas from scratch very occasionally, and then primarily use the output or just make minor tweaks as the system grows (yes, there are a small number of enterprise architects who design schemas constantly, but they are rare enough and use tools like this rarely enough that Microsoft already removed much of its architectural design tooling from the high end Visual Studios SKUs because their research showed it was not used enough to justify the maintenance cost).
Highly intermittent usage by normal devs doesn't lend itself well to a subscription model. Focusing on a tiny number of high usage enterprise architects forces much higher per seat pricing because the volume is so low, further lowering the volume. "One-month access" or similar less-than-a-year time limited access doesn't lend itself well to "I don't know how long this will take for me to design." Annual pricing probably ends up needing to be high enough that devs will simply fall back to what they were doing, which is use a text editor with no specialized visualization.
It looks like a fantastic product. I'm worried it's much less fantastic a business.