Been building Voiden, an API IDE on Electron. Not really “just an API client”, and not a(nother) thin wrapper around a webapp either.
Made it intially available for Windows and Mac, but after getting requests from folks who work on Linux, we added Linux support a few months ago, before open-sourcing it. (That's actually one of the reasons we picked electron :to be able to ship fast and have cross platform consistency across Linux, Mac and Windows.)
Repo: https://github.com/VoidenHQ/voiden
So far, Voiden is available on Linux via:
- .deb for Ubuntu and Debian-based distros .rpm for Fedora, RHEL, and other RPM-based distros
- .AppImage for a portable option that should work across most distributions
- .AUR package for Arch users : https://aur.archlinux.org/packages/voiden-beta-appimage
Definitely considering adding more like Nix or Flatpak, but we are working to get our priorities right: Which ones would you actually use and prefer?
A disclaimer about the tool: Since we didn't want to build yet another (cheaper) clone of Postman, Voiden looks and feels very different:
-
The UI is "programmable": Requests are “built” with slash commands from blocks (endpoints, headers, auth, params, bodies, etc.), like LEGO blocks but for API components. Or like Notion for APIs.
-
These blocks can be also reused in different APIs to have ALL common elements done in one single file. You can then change them once and it will all get updated in all the other docs. Just like in code when we add an extra logic to an imported method. (In other API clients you would need to duplicate stuff or just use environment variables to substitute.)
-
API Specs, tests, and docs live together in executable Markdown.
Welcome to try it out and let us know: what works, what breaks, and which packaging or distro support would make Voiden easiest for you?
Strong opinions are encouraged. :)
Github : https://github.com/VoidenHQ/voiden Download here : https://voiden.md/download
Git native, No login, No accounts, No telemetry.
Hey yes will do. Flatpak is something we see considering/working on.
Notion in the sense that it adapts to the user. We like this idea : that you can use Notion for literally Amy document you want.
In the same way, when one open Voiden they can "program" the interface with slash commands and add headers, auth, documentation etc in any way they like. So in Voiden we bring specs, tests and docs together in one single file. In the same way that you can use notion to bring different lists, blogs, ideas etc into the same place and collaborate. The difference and the power of Voiden is that everything you add in the Voiden doc is executable, meaning you can run the tests in the same place and keep the docs and the context (that might be on slack or anywhere else devs talk) together.
Basically the notion like refers to the philosophy of the tool to not force a fixed UI to the user and allow for different use cases and scenarios. Does it make sense?
We are also calling it Lego for APIs for the same reason plus because of the fact that you can use blocks to compose requests but also reuse them for multiple requests that share some similar components.