kiselitza

Joined 3 years ago

Karma

Submissions

Member since

Dec 11

Freelance Head of DevRel

You’re building a dev tool or a dev-facing tech product? Looking to get that tool in front of your ideal tech audience? Trying to reduce churn and friction, make your users` lives easier?

Or maybe you’re a VC looking to invest in devtools? Reach out, let’s build your strategy together!

View on Hacker News

Recent submissions

Comment · 1 year ago

What's your use case? What are you looking for in an API tool?

I'm helping build https://voiden.md/ We just dropped a major beta, FOSSing it by the end of the year.

Comment · 1 year ago

That's quite a list! Have you by any chance stumbled upon Voiden thus far?

It just got a major beta release, and is aiming to open source in the following couple of weeks: https://voiden.md/beta

Comment · 1 year ago

It's always the "it depends" kind of answer. In bigger companies, you have teams dedicated to API governance, whatever they say, it's how it's done. In early-stage startups, you have full-stack folks doing end-to-end design, test, integrate with UI, document, etc. The trickiest ones are the ones that are in between these two stages. It's where it gets messy, and you MUST have something in place to serve as an API contract. Swagger dominates that, imho, Postman collections and docs are used a bit differently in my experience.

I'm helping build https://voiden.md which serves as a unified place for API spec, test, and documentation, but there are also plenty of API tools that focus solely on endpoint execution.

Comment · 1 year ago

Hi, thx for the feedback! Testing the settings (including different themes and font sizes as we speak). Some tweaks are been made on the responses side as well. As per the rest of your comments, some of these things have been discussed or touched upon, others have been just added to the discussion board :)

Comment · 1 year ago

Hi! Thx for that. Can you please open an issue with a screenshot here: https://github.com/voidenhq/feedback

What you're saying doesn’t sound familiar whatsoever, but I'd really like to look more into it.

Comment · 1 year ago

And yes. It's completely free. With plugin extensibility for anyone to build/install whatever they want.

The CEO committed to open-sourcing it, as well as to not monetize on anything that doesn't introduce operational costs to the team.

https://voiden.md/blog/why-we-rebuilt-bloated-api-tooling

Comment · 1 year ago

Ah, yes, the cloud-dependent tool that forces you to pay per seat and log in for any type of collaboration is down when their cloud provider is.

Anyways, the folks have spoken, no need to double down. There are more than a dozen alternatives to it, and new ones are coming up.

I'm helping build a new one.

- Completely offline.

- Gives the ability to build reusable blocks (headers, query params, etc)

- Let's you document everything in Markdown.

- Imports your collections and cURLs.

https://voiden.md/

Comment · 1 year ago

I'm helping build Voiden: https://voiden.md But am thinking of a LOT these days, really, saw a bunch of interesting APIs on https://apyhub.com/catalog recently, so might go on and tackle a few of these.

Comment · 1 year ago

I mean, IF the API is primarily tailored for UI presentation, there's already a text/html that you can use. I don't see the real problem here. Unless it's a type of API that has multiple purposes. In which case you got to tailor the response/presentation based on the needs.

Either way, the time needed to build a HTML elements will be eventually spent somewhere, on the server or on the client side. Server provides you with the data, you pick the form in which it is sent, and then work around the presentation layer.

I'm helping up the team behind https://voiden.md so I can tell you, it's easy to present the HTML even in the API clients, let alone the website itself.

Comment · 1 year ago

A TL;DR of it is that for teams behind APIs, building, documenting, and testing APIs feels all over the place nowadays. It's a pain, it wastes time, causes errors, and frustrates everyone involved.

This post dives into why API tooling is such a headache, why the industry keeps making it worse, and how Voiden attempts to make life easier for developers.

Comment · 1 year ago

Totally agree on this. There are things that belong in cloud, even a 3rd party one. Not everyone has a luxury of self-hosting. But keeping API secrets in any 3rd party cloud is just insane imho.

Comment · 1 year ago

Working on it. It's hard to explain to devs who used to something how bad that something is. Especially when it once was awesome.