[callmekatootie]

My main grouse with these REST GUI clients is how much memory they consume. Maybe because they are electron apps in the end, but it's just funny that nobody's devoting any time to create native apps anymore for something that should be a utility and not the main app.

[_fat_santa]

Not sure about Windows but for MacOS, Paw is an excellent Native app. Thought not worth the $50 for me since I hardly ever work on API's.

[ideologysec]

dunno your operating system, but Paw for macOS is a great native REST/API GUI client.

https://paw.cloud/

[eyelidlessness]

I haven’t used Paw because I have very little need for a tool in this category lately, but I’m tempted to buy it anyway just to reward them for developing a good native Mac UI, and not restricting it to a subscription model.

[rubyist5eva]

ironically, they have a not-mac version that is electron based

[slim]

it should be a browser developer tools addon

[nwsm]

Most devs who use something like Postman in their normal workflow would prefer a standalone client (or cli).

[notpushkin]

I'm working on something a bit orthogonal, but similar in spirit: a “network requests” tool, similar to the Network tab in Devtools, but batteries included and working _both_ as a browser extension and a reverse proxy standalone app – so you just pick whatever suites your workflow better today. It's still super early stage though.

[thefunnyman]

In Firefox dev tools you can replay and modify requests which isn’t something I’ve found in chromium browsers.

[TameAntelope]

Why would I use a browser developer tool to test an API? A browser is wholly uninvolved in API development.

[slim]

because the browser is literally the HTTP client. why would you need to use something else for a very specific case of HTTP protocol interaction ?

[TameAntelope]

Because a browser is not the HTTP client.

[tomc1985]

It still makes calls, and a proper REST client means you can make POST/PUT/etc on command

[getcrunk]

That's only true if you aren't testing in prod