Hacker Newsnew | past | comments | ask | show | jobs | submit | theFluke's commentslogin

If you're on macOS, Auxl (https://auxl.io) is another option to try. Support for gRPC should be coming soon. Disclosure: I am the author.


Yep, it does!


I personally often need the output from one service as input for another. With the new input often requiring a transformation. Auxl can function as a low friction environment to organise that without it getting cluttered.

I also think a lot of API clients tend to obfuscate flows like, for example, an OAuth authentication. Making each step visible and having that extra granularity can help with customisation and debugging.

Other than that, purely from a usability perspective, I think it’s fun to use.


Auxl looks good in that respect but maybe I wasn't clear enough in my question.

What's the typical use-case of apps that let you make requests to APIs via a GUI?

I've used them _briefly_ as part of a development process before, but never enough to justify buying one (I'd just spend a couple of minutes longer to write a Python script). Is that what most people are using them for? Am I missing a use-case?


It’s a tool in a developers toolbox. Some use it, some don’t. Similar to the debugger vs printf debate.

These apps can be useful for testing, developing and exploring APIs and they can function as GUI for services that don’t have one.

For example a former client used Postman as a client to perform administrative tasks for which there was no UI yet. Most of these tools have feature to save common request flows and share them with your team.


I think the market here is people that can't or won't crank out a script or CLI to do the same thing. That audience has become relatively fair in size as programming has grown.


Paw's great for figuring out someone else's poorly documented API. Sure I could code up the equivalent, but not going to waste cycles reinventing a tool that pays for itself in less than an hour of saved time


I think it's a creature-comfort for webdevs who don't like getting their hands dirty.


Auxl has a modular design, which can make chaining requests more intuitive. It’s also native, which still matters to many.


Also support for Websockets and chaining those w/ rest calls. (I know insomnia doesn't support this, dunno about others)


I'm guessing you mean "local" rather than "native" as the alternatives posted in previous comment are native for their platform too, just like Auxl.


I meant native as in not fully built with web technology. Which, if I'm not mistaken, the alternatives posted in the previous comment are.


I’m personally not sure that is a factor for many users, a good web app is as good as a good native app on modern hardware


I guess it depends how you define many, but I’ll take a native application over HTML any day.


Many macbook developers do care if it's a native app or a battery draining chrome embedded app.

Kinda defeats the purpose of having a specialized CPU, OS & software to optimize battery usage.


that matters, at least to me. that makes me prefer Paw over Insomnia and Sublime/neovim-kitty over VSCode


I have pretty beefy hardware so I don't notice the diff in terms of performance. I do however appreciate that the battery life isn't sucked down hard by native apps the way electron does. just having chrome open significantly affects my battery life.


I only want apps built with Electron or similar! Makes it easy for me to switch platforms, they get developed faster, they're easier for me to contribute to and they are infinitely more hackable.

Imagine optimizing your dev tools for battery life? As if I want to work on a single tiny screen all day...or in meetings, hotels, planes, trains...


Others do like to travel and be able to work without their battery dying within a couple hours.

If you like wasting your battery that's fine, but not the typical use case for someone with a portable device.

The screen size thing is a separate issue and alleviated by using screen switching gestures or a secondary screen using an iPad.


Here's an example that I encountered recently:

https://stackoverflow.com/questions/58657087/after-upgrading...


That version of Xcode has been pulled because of this issue.


To be fair, that's not an issue in the Swift runtime.


Now everyone can have their very own custom recipe app.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: