Hi HN! I'm Greg and I've been working on Yaak for just over a year. I usually describe it as a Postman alternative since most developers are familiar with that, but it's targeted more toward users that just want an API client (no mocking, testing, spec design, etc).<p>Having also created Insomnia for a similar purpose, I never thought I'd build another API client again. But, after selling Insomnia in 2019 and watching it expand into the broader feature set of Postman, I was left wanting a simpler tool again. Yaak was my answer to that.<p>It's hard to describe how it's better than the 100 other API clients, since its main benefit is design, but there are a few stand-out features:<p>- Optionally sync data to a local directory as plain-text, for use with Git/etc
- Build and install plugins for authentication, template functions, or generic actions
- Support for REST, GraphQL, WebSocket, server sent events, and gRPC<p>Yaak requires a license for commercial use but this only applies when using the prebuilt binaries. If building from source, a license is not required.<p>It's available for Mac, Windows, and Linux and the source is at <a href="https://github.com/mountain-loop/yaak">https://github.com/mountain-loop/yaak</a><p>I'd love to hear you think!
The Software tool lifecycle:<p>1. Dev makes a cool lightweight productive tool<p>2. Tool becomes popular<p>3. Company buys tool<p>4. Company adds a bunch of shit nobody needs making the product bloated and annoying to use.<p>5. Dev makes a cool lightweight productive tool
This is excellent Greg thanks for sharing!
One thing I do find missing from a lot of these API clients is synced environment variable entries between environments.<p>For example if I create a `dev` environment that contains a `base_url` environment variable, it's expected that when I create a `prod` environment, it will also have a `base_url` environment variable. Then in the future if I add more environment variables to my `dev` environment, I need to duplicate the work of adding an environment variable entry to `prod.<p>I can't be the only one that experiences this pain :P
The UX of this could be handled in any number of ways:<p>- When you create a new environment, ask if you want to duplicate an existing environment's variable names (with empty values)<p>- If you add a new environment variable, ask if you want to add the environment variable name to another environment<p>- Option to enable syncing between all environments i.e. deleting a variable row in one environment deletes it for the rest
etc<p>I was about to post this as a github issue for traction but given Issues are turned off thought this may be the next best place.<p>Regardless, Yaak is excellent!
> Yaak is still open source under the MIT license. You can view, modify, and run the source code for both personal and commercial use. Licensing applies only to the prebuilt binaries.<p>That's a pretty interesting pricing strategy. I think REHL is the only other project I saw with this type of pricing.
I’ve been using Yaak for a few weeks now and it’s great.<p>I bounce around API clients a lot because the UX just never feels right, they always get in the way or start to feel clunky sooner or later.<p>With Yaak it feels natural, it’s clean and simple and is a joy to use.<p>I’m looking forward to seeing it grow and improve further.<p>I just hope as its feature set grows it can hold on to that simplicity. Hopefully the plugin system can be used to bridge any gaps without overloading the main app.
Ah! I was so happy I can put postman to rest. What I didn't like is the landing page did not clearly communicate I am installing a non-free product with a trial, so I uninstalled it. I am only letting you know that this trick might affect retention.
Yaak is great, I have been using it since the launch Greg.<p>I'm kind of curious why you picked Tauri over Electron for this one? I know one big benefit is smaller binaries but I'd love to know your thoughts behind this decision.
How can we be sure that Yaak won't be sold and enshittified two years from now?<p>Maybe I'm nitpicky, but I love sticking to software for years, had to ditch Insomnia after an auto-update killed my collections and wanted me to sign up for a cloud service. Could happen with this (yes, any software for that matter), too, because you'll sell it in a year from now.
Did you consider JetBrains licensing model? I don't like renting software, I'd rather buy it upfront, but JetBrains with their fallback licenses really got me – you get your perpetual fallback license for a particular version of product. And guess what, I keep paying them anyway, because of confidence I can fallback, but they keep innovating with new updates.
fantastic. i was about to make my own after being frustated with bruno's change in billing and just lack of quality.<p>having gone from postman -> insomnia -> back to postman -> bruno - id like to just have something simple that _just works_ without making it a pain.<p>looking forward to giving this a spin.
> But, after selling Insomnia in 2019 and watching it expand into the broader feature set of Postman, I was left wanting a simpler tool again. Yaak was my answer to that<p>I'd love to read about your experience building two distinct but similar products in the same space years apart
What about a license for devs to use when it’s commercial, but their company won’t buy it?<p>Kind of like how Quokka has a “personal pro” license.<p><a href="https://quokkajs.com/pro/" rel="nofollow">https://quokkajs.com/pro/</a>
I use yaak! Great piece of software for just not having to memorize curl syntax, wrestle postman<p>What’s the end goal though? Planning to sell a licensed version? I’d be happy to pay for a model where I can own it for life but only get updates for a year.
Thought this was about the language learning app <a href="https://yakk.app/" rel="nofollow">https://yakk.app/</a> for a brief moment looming at the URL!
Looks great!! I would love to move to this as my go-to API client but my fear is it stops getting maintained overtime like httpie.io but at least this is open source so a great win!
Cool stuff, how does it compare with httpYac?
> <a href="https://httpyac.github.io/" rel="nofollow">https://httpyac.github.io/</a>