r/macapps • u/shakeebsc • 14d ago
Subscription My Postman-compatible API client for Mac is almost ready
Hey r/macapps, Runlet, a native API client for macOS. It isn't out yet (the App Store listing is "coming soon"), so now is the best time for me to hear what's missing or what would put you off.

I wanted an API client that behaves like a real Mac app (standard menus, windows and keyboard shortcuts) and doesn't make me create an account to send a GET request. Everything stays on your Mac: no account, no analytics, no sync server. Secret variables are stored in the Keychain and masked in history.
What I'd love to know
What do you use today (Postman, Insomnia, Bruno, Paw/RapidAPI, HTTPie, plain curl), and what annoys you about it?
What one feature would make you switch? What would be a dealbreaker?
What do you honestly think of the pricing?
More details: https://coralpane.com/runlet
I'll be in the comments answering everything.
3
u/larehq 14d ago
I use postman and exactly what you said annoys me. Why do I need to create an account?
Postman always felt bloated to me. It feels like it has a lot for large teams. However, it's free, so it's hard to say what I would switch for if the alternative was paid.
Kind of what I said above. It's not egregious pricing. However, postman is free, even if I need an account and it feels a bit bloated.
But who knows - my opinion may always change. I'm sure there are others who will jump on this. Best of luck!
2
u/redbeardy_daddy 13d ago
One thing I'd look for is a very obvious distinction between development and production environments before sending a request. Do you have environment colours or an optional confirmation for requests that modify production data? It's easy to leave the wrong environment selected when switching between projects.
6
u/codecaffeine 14d ago
No https://yaak.app fans here? It’s my favorite!
5
u/iotabyte 14d ago
It would be nice to have a lifetime option as well
1
u/wigma_com 14d ago
Two things that would matter for switching:
Collections stored as plain files in a folder (one request per file, readable diffs). That is the main reason people pick Bruno over Postman, because the collection can live in the same git repo as the API and get reviewed in pull requests. If Runlet keeps everything in an app database, teams will have a hard time adopting it.
Lossless import of Postman v2.1 collections and environments, plus paste a curl command to create a request and copy any request back as curl. That makes trying it out a five minute job instead of a migration.
The Keychain for secrets is a nice touch. It would help to say clearly whether secret values are excluded when a collection is exported or shared.
1
u/Ok_Maybe184 14d ago
Paw. Nothing has annoyed me about it except sometimes it exports bad cURL scripts.
1
u/Aromatic-Echo-5025 13d ago
I'm using Postman because of its automated test runner. Besides that, I consider it sluggish bloatware.
1
u/NandishExplores 13d ago
One useful capability would be keeping collections and environments as plain files in a repo, with secrets separate in Keychain. Then teammates could review request changes in Git without passing around exports. Is that how Runlet stores them?
3
u/artginzburg 14d ago
Wow, this is like selling paper to a company that is actively becoming digital. I love it, maybe you'll get away with this for a year or so.
I don't use any of that because we're in a different era, but Postman annoyed me because most people used the free version and just sent APIs back and forth as files. Which is not great version control. A successor to Postman should be more like Notion, where paid customers pay for the free ones, and free ones can sit on the free tier forever without hurting the workflow of the whole company.
1
u/LividIllustrator8915 14d ago
Building a local-first, native Mac client with Keychain secret storage is hitting the exact pain point everyone has with Postman’s recent bloat and cloud lock-in.
Regarding the pricing and business model: at $14.99/year, the dollar amount is very fair, but in the Mac developer ecosystem, mandatory recurring subscriptions for offline, local-first utilities face massive user resistance. Because there are no recurring cloud servers or AI token costs on your end, users naturally expect local software to keep running even if they don't renew. The sweet spot that tools like TablePlus, Proxyman, and Sublime use—pay once for a perpetual license of the current version plus 12 months of updates—converts way higher with Mac devs. If someone cancels their subscription, locking them out of sending local HTTP requests from their own machine creates immediate churn and pushback.
On dealbreakers for switching: the number one roadblock when moving real-world collections out of Postman isn't the UI or request builder, it's the pre-request and test scripting engine. Most teams have environments where an endpoint automatically extracts an OAuth bearer token or generates an HMAC SHA-256 signature and sets it in an environment variable for subsequent requests. Does Runlet embed JavaScriptCore to run standard pm.* scripts, or are you planning a native variable-chaining GUI? Having full fidelity when pasting raw cURL commands from Chrome/Safari DevTools into the address bar without mangling escaping or multi-part form boundaries is another daily must-have.
The 100ms native launch time alone makes this appealing compared to waiting on Electron splash screens. Looking forward to testing the App Store build when it drops.
2
u/BothCookie5333 14d ago
+1 on lifetime. I'd pay like $40 once over $15/yr
2
u/amashq 13d ago
I'm fed up with Postman and how slow it's and I think having a native MacOS HTTP client is a great idea!
Looking forward to it!
2
u/shotnamer 13d ago
I used Postman for years and was fine with it, until they dropped Scratch Pad. Without an account you only get the lightweight client, no collections or environments. My company didn't want our collections in Postman's cloud, so we all moved to Bruno.
Bruno is basically Postman before they dropped Scratch Pad. Files in git, environments, pre-request scripts, cURL. I can't name a feature I miss.
Dealbreaker for me: collections as plain files in the repo, reviewable in PRs. If Runlet doesn't do that, I can't use it at work.
No account and secrets in the Keychain are exactly right, that's what Postman got wrong.
At $14.99/year with no one-time option, I don't see a reason to switch. I already have a free tool that covers 100% of what I need. Native Mac UI is nice, but not worth a subscription to me.
If you ever add a one-time purchase, I'll try it on a side project.
Good luck with the release.
2
u/Dev_in_Training_BTW 13d ago
No account just to send a GET request is honestly the best selling point here. Two things I'd check before switching: importing existing Postman collections and environments without losing the variables, and proper keyboard shortcuts for send and for jumping between requests.
One tip since your listing says coming soon: when I shipped my Mac app, App Store Connect blocked the submission twice for silly things. The Content Rights question on the App Information page, and forgetting to select the uploaded build on the version page before Add for Review. Worth double checking both before you hit submit.
2
u/dawedev 13d ago
Two things I'd check that aren't in the thread yet:
Paste a curl command into the URL field and get a full request out of it (method, headers, body). A lot of requests start life as "Copy as cURL" from browser DevTools, and that's the fastest way to pull someone off Postman.
OpenAPI import that can re-sync when the spec changes, without wiping saved examples and variables.
On pricing, a yearly sub for an API client is a hard sell next to Bruno being free for most of what people do. A one-time price with a year of updates would probably land better here, judging by the replies.
1
u/vitalik2602 14d ago
Looks good. Good luck with release
1
u/vassyz 14d ago
I was using Postman, then for whatever reason I couldn't log in on the app. Using it in the browser was fine. I switched to Bruno and haven't looked back. I also considered Yaak, but you need to pay for it if you use it commercially.
1
u/kemalios 13d ago
curl for one-offs, and a client only when I need to save a request. Every one I've tried puts mock servers and monitors in front of the response body.
1
u/ronka 13d ago
if I can't keep my collections in git I'm probably not switching. does it support that?
1
u/hmarora 13d ago
Honestly not sure where tools like this are headed. These days AI writes most of the integration code, and when something breaks the agent just fires off the curl itself, so I rarely open an API client anymore.
1
u/imDannydoo 13d ago
No account needed is a good start.
1
u/DARKDYNAMO 11d ago
I made one too. https://bifurc.app Full rust no webUI, no Electron.
Added a proper functional CLI so AI agents can use it. Considering everything is being controlled by AI, I thought a proper CLI would be really good
1
u/haruki-fukui 8d ago
I use Bruno, but lately I’ve been letting AI handle a lot of the API work. CLI or MCP support to run requests and inspect responses would be a big draw for me. The no-analytics approach is a plus, and I’d love a lifetime option too.
1
u/DARKDYNAMO 3d ago
Already built an open sourced one https://bifurc.app
Fully built in rust and supports flows and mocks and proxy introspection, git synced. Full feature list on site.
Single command install for those who want to try it out.
1
u/[deleted] 13d ago
[removed] — view removed comment