What are the typical use-cases for things like this?
I've used Paw and Postman in the past, but never for more than 2 endpoints in one go, never for more than an hour or so in one session. I've only ever got value out of them as "slightly quicker than a Python notebook" solutions for testing out a hypothesis.
The only other thing I can think of is maybe as a way to pass the understanding of an API's nuances from one developer to another, but I've never needed to do that at any higher level than writing the one-weird-trick to make it work into an email to pass on that knowledge.
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.
The “pay for it once, own it forever” is appealing. However. I think recent engineering has shown this to be unsustainable. My initial thought was “they don’t plan to update this; no point buying in”.
It always fascinates me when I see Max/Live/etc. mentioned on Hacker News. You wouldn't think the overlap between the user demographic would be very large, y'know?
There's no way that I'd be caught dead paying $30 for this when there are tons of platforms online that do this for free. What is the value proposition here?
What do you think of Paw (https://paw.cloud/) which has some overlap with Auxl and charges more and has been in business for over seven years based on a similar value proposition (native app for one platform with free alternatives)?
skrowl|4 years ago
theFluke|4 years ago
danpalmer|4 years ago
I've used Paw and Postman in the past, but never for more than 2 endpoints in one go, never for more than an hour or so in one session. I've only ever got value out of them as "slightly quicker than a Python notebook" solutions for testing out a hypothesis.
The only other thing I can think of is maybe as a way to pass the understanding of an API's nuances from one developer to another, but I've never needed to do that at any higher level than writing the one-weird-trick to make it work into an email to pass on that knowledge.
theFluke|4 years ago
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.
the_other|4 years ago
grishka|4 years ago
bubblesorting|4 years ago
Malp|4 years ago
Cybotron5000|4 years ago
unknown|4 years ago
[deleted]
pqb|4 years ago
atarian|4 years ago
claymav|4 years ago
moltar|4 years ago
theFluke|4 years ago
PostThisTooFast|4 years ago
[deleted]
smoldesu|4 years ago
robenkleene|4 years ago