Kinda defeats the purpose of having a specialized CPU, OS & software to optimize battery usage.
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...
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.
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 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.
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?
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 mean, the core value proposition here is quite good. I've been wanting something like this for awhile. but I'd feel a nervous staking my entire testing flow on a product which has no incentive for ongoing maintenance.
I'll definitely purchase it. I can easily justify it as a business expense and I hope the author of the software finds ways of plugging this product into a larger saas offering so he can continue paying his bills by maintaining this.
THis product seems pretty useful. I'm building out a graphql api and end up haveing to maintain scripts to test out various workflows. this would be way simpler to drag and drop together a workflow for testing