It seems really neat, but it's unclear what problem you're solving.
Is the goal of the project to let people write documentation for APIs, explore APIs, or something else?
Here are a few suggestions:
1. Start with a clear story of why you built this. Not lock in etc, but what were you or your team trying to do? That will help me understand whether I too try to do this thing.
2. Now you can tell me about all your frustrations, and I as a fellow misery drenched individual will say "Yes! I too have suffered the lack of cloud sync lock-in!"
3. Let me see it! Is there a way to embed the actual editor in the browser? Barring that putting a heading over the video, or a caption telling us what you're doing. When I click around to explore, let me click on those screenshots so I can see what you've built.
All in all, this looks really neat, but the challenge with building something divergent is that you need to invest more effort in telling the story.
I've been reading this one and then the post itself a couple of times.
Appreciate the suggestions and the time you took to write them down.
Just not sure if those would help here (not saying they 100% wouldn't). I am all for storytelling on some platforms, but HN is IMHO a no-bs, no fluff, keep-it-short and to-the-point space.
If you're a dev, and you excessively ran APIs or governed them, you most likely remembered the pains mentioned later in the post the second you came to "API client" bit. The frustration bit should tell you why it's not just another one of those tools but rather addresses those pains. And the example is showcasing the minimum effort needed to execute an endpoint.
If I were to rewrite it again, I don't think I'd change much, if anything.
> If you're a dev, and you excessively ran APIs or governed them…
I am a dev, and it took me a while to realize this was the pain point you were solving. Mayhaps I'm the wrong dev, and that's just fine, regardless this looks pretty neat.
Or maybe I'm the wrong storyteller for you :D
We did get a couple of pieces of feedback re- the landing page not being clear. I'm wondering if you checked the website before or after reading my copy? Would you say that may have impacted this "time to realisation" span?
Is the goal of the project to let people write documentation for APIs, explore APIs, or something else?
Here are a few suggestions:
1. Start with a clear story of why you built this. Not lock in etc, but what were you or your team trying to do? That will help me understand whether I too try to do this thing.
2. Now you can tell me about all your frustrations, and I as a fellow misery drenched individual will say "Yes! I too have suffered the lack of cloud sync lock-in!"
3. Let me see it! Is there a way to embed the actual editor in the browser? Barring that putting a heading over the video, or a caption telling us what you're doing. When I click around to explore, let me click on those screenshots so I can see what you've built.
All in all, this looks really neat, but the challenge with building something divergent is that you need to invest more effort in telling the story.