I really like paw but can't say I've tried the alternatives. I needed a thing, it was in the AppStore, go.
Paw – macOS HTTP client for testing and describing APIs
61–70 of 121 posts
Re: Paw – macOS HTTP client for testing and describing APIs
#62For quick-and-dirty things I use cURL or httpie otherwise I use Paw (and have for about a year now). I had previously used Postman before that, but even then Paw was a better app—native app so it looked better + felt faster, nicer collections, better default shortcuts, etc. Paw has a lot of power behind it, otherwise if you're just doing basic POST requests, stick to httpie. The code generators and extensions are nic…
You can copy a browser request as a cURL command. Both Firefox and Chrome via developer tools. Just a cool feature I learnt recently.
Seems useful. Thanks for sharing.
Re: Paw – macOS HTTP client for testing and describing APIs
#63For quick-and-dirty things I use cURL or httpie otherwise I use Paw (and have for about a year now). I had previously used Postman before that, but even then Paw was a better app—native app so it looked better + felt faster, nicer collections, better default shortcuts, etc. Paw has a lot of power behind it, otherwise if you're just doing basic POST requests, stick to httpie. The code generators and extensions are nic…
Just to play devil's advocate: I do all of that in Postman, which for the last year or so has also been a native app - at least, in the sense of being non-Chrome, it's not using macOS UI elements. I think different environments is a recent feature too. It's free, and cross-platform. And the team sharing capabilities are cheaper than Paw's. It's odd that Paw seems to bill its single platform nature as a feature. There…
For Mac users t is a feature, it means 100% dev focus on their platform and tight integration/up to date ness with all Mac features. It’s also obvious a problem, if they have windows users team mates or friends. It’s got pros and cons.
Re: Paw – macOS HTTP client for testing and describing APIs
#64I have a Paw license and recently I started using Insomnia instead: https://insomnia.rest/ I find Paw's project management very annoying. It assumes that I am working on some project and wants me to organise everything like that. Fine, lets do it, so where are my projects? They are hidden in some dropdown that you can have fun finding. Insomnia is much cleaner and more to the point.
Thanks for mentioning this! Simplicity and ease of use is exactly why I started building Insomnia. Awesome to see that others agree.
Really love Insomnia. Also really appreciate the account syncing available with pro.
Re: Paw – macOS HTTP client for testing and describing APIs
#65Earlier quoted context omitted.
This is my first time hearing about `SetApp` but it sounds like an interesting concept. How do you feel about it? How many apps from it so you use often/daily? Worth the $10 a month?
I had a trial and found the selection for developers wasn't worth the $10. There are a few little utilities, like the Regex tester, that are definitely neat and well made, but given the once a month I actually need that functionality, I'll just use a crappy web app for it. Most of the software I found to be the 3rd best in its category (or worse), for example, It doesn't have OmniFocus or Things, it has a bunch of to…
but OP's point is that a Paw subscription /alone/ is $12/m
Re: Paw – macOS HTTP client for testing and describing APIs
#66Paw's killer feature for me is request chaining
GET /things -> GET /things/{things.first.id} -> PUT /things/{things.first.id} -> DELETE /things/{things.first.id}
Re: Paw – macOS HTTP client for testing and describing APIs
#67Earlier quoted context omitted.
What differentiates Insomnia from Postman? Both are non-native electron apps.
There are so many differences it's impossible to list them. In general, Postman focuses on having every feature under the sun (integration testing, mock APIs, etc) whereas Insomnia focuses on the core of just being an HTTP client with additional helpers to be more productive. The result being that Insomnia is not suitable for as many use cases but is has a better user experience because it's more focused. Insomnia is…
Totes. Another issue I've found (at least with the browser extension flavor), is that even though it is a separate window, Cmd+Tab switching between apps is totally broken by Postman. The Postman window will completely take over your Chrome instance.
Also, I'm glad I found you! Long-time user of Paw, but going to make the switch to Insomnia. Question, can I just type a JS object into request body and you stringify the JSON for me? Is that something you would accept as a PR if not?
Re: Paw – macOS HTTP client for testing and describing APIs
#68Earlier quoted context omitted.
Just to play devil's advocate: I do all of that in Postman, which for the last year or so has also been a native app - at least, in the sense of being non-Chrome, it's not using macOS UI elements. I think different environments is a recent feature too. It's free, and cross-platform. And the team sharing capabilities are cheaper than Paw's. It's odd that Paw seems to bill its single platform nature as a feature. There…
For Mac users t is a feature, it means 100% dev focus on their platform and tight integration/up to date ness with all Mac features. It’s also obvious a problem, if they have windows users team mates or friends. It’s got pros and cons.
Does that matter without knowing the size of the team? If the team's 10x bigger than you'd have guessed, is it still worse if they're working on Windows & Linux platforms too?
FWIW, I do use macOS, I just thought it was an odd 'feature', not least because it makes it unportable and contributes to lock-in.
Re: Paw – macOS HTTP client for testing and describing APIs
#69Been on the Insomnia REST client bandwagon since they were in beta https://insomnia.rest/ ... went to checkout this page and saw no reason why I'd want to change.
Re: Paw – macOS HTTP client for testing and describing APIs
#70Earlier quoted context omitted.
For Mac users t is a feature, it means 100% dev focus on their platform and tight integration/up to date ness with all Mac features. It’s also obvious a problem, if they have windows users team mates or friends. It’s got pros and cons.
Does that matter without knowing the size of the team? If the team's 10x bigger than you'd have guessed, is it still worse if they're working on Windows & Linux platforms too? FWIW, I do use macOS, I just thought it was an odd 'feature', not least because it makes it unportable and contributes to lock-in.
Hmm that’s a good point, I hadn’t thought about team size. Although even with a large team, there may be limits to what you can do if the product must be cross platform. It’s funny I use windows myself so this is not a feature for me, I’m really just trying to see it their way that’s all.