Skip to content Skip to footer
0 items - $0.00 0

Show HN: Yaak – An open source, Git-friendly desktop API client by gschier

Show HN: Yaak – An open source, Git-friendly desktop API client by gschier

Show HN: Yaak – An open source, Git-friendly desktop API client by gschier

12 Comments

  • Post Author
    DrBenCarson
    Posted February 26, 2025 at 9:00 pm

    This got much less attention than I would have expected.

    Yaak is awesome, please please please keep it local-friendly

  • Post Author
    dhruvkb
    Posted February 26, 2025 at 9:06 pm

    Would love to see a comparison with Bruno[1].

    [1]: https://usebruno.com

  • Post Author
    codecraze
    Posted February 26, 2025 at 9:43 pm

    Congratulations !
    Will test this out tomorrow :)

  • Post Author
    czhu12
    Posted February 26, 2025 at 10:35 pm

    I use yaak! Great piece of software for just not having to memorize curl syntax, wrestle postman

    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.

  • Post Author
    sunnybeetroot
    Posted February 27, 2025 at 6:01 am

    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.

    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.

    I can't be the only one that experiences this pain :P
    The UX of this could be handled in any number of ways:

    – When you create a new environment, ask if you want to duplicate an existing environment's variable names (with empty values)

    – If you add a new environment variable, ask if you want to add the environment variable name to another environment

    – Option to enable syncing between all environments i.e. deleting a variable row in one environment deletes it for the rest
    etc

    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.

    Regardless, Yaak is excellent!

  • Post Author
    opem
    Posted February 27, 2025 at 8:40 am

    Yaak is so underrated!

  • Post Author
    martin_a
    Posted February 27, 2025 at 3:57 pm

    How can we be sure that Yaak won't be sold and enshittified two years from now?

    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.

  • Post Author
    unchar1
    Posted February 27, 2025 at 4:13 pm

    > 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.

    That's a pretty interesting pricing strategy. I think REHL is the only other project I saw with this type of pricing.

  • Post Author
    dban
    Posted February 27, 2025 at 4:27 pm

    > 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

    I'd love to read about your experience building two distinct but similar products in the same space years apart

  • Post Author
    denvermullets
    Posted February 27, 2025 at 4:35 pm

    fantastic. i was about to make my own after being frustated with bruno's change in billing and just lack of quality.

    having gone from postman -> insomnia -> back to postman -> bruno – id like to just have something simple that _just works_ without making it a pain.

    looking forward to giving this a spin.

  • Post Author
    yoyohello13
    Posted February 27, 2025 at 4:39 pm

    The Software tool lifecycle:

    1. Dev makes a cool lightweight productive tool

    2. Tool becomes popular

    3. Company buys tool

    4. Company adds a bunch of shit nobody needs making the product bloated and annoying to use.

    5. Dev makes a cool lightweight productive tool

  • Post Author
    tv10
    Posted February 27, 2025 at 5:33 pm

    I love your landing page & overall design of the home page. So clean. Love the color scheme as well.

Leave a comment

In the Shadows of Innovation”

© 2025 HackTech.info. All Rights Reserved.

Sign Up to Our Newsletter

Be the first to know the latest updates

Whoops, you're not connected to Mailchimp. You need to enter a valid Mailchimp API key.