NoMac.app - The headless iOS app publishing pipeline for AI agents.
by•
The native app publishing pipeline built for AI agents: build signed iOS releases to validate your code, push to TestFlight ot see preview on your iPhone in minutes, and submit to the App Store directly form your agent. No Mac, no Xcode, all from your Claude, Codex, or Cursor agent via NoMac CLI and MCP.
Replies
NoMac.app
cool idea, I was thinking of launching an iOS app but having to get Xcode and a newer mac to run it was annoying. How is using this better than me just asking claude code to make it for me on a PC?
NoMac.app
@mjohnson42Â Claude Code can absolutely write the app for you on a PC. The problem comes after that: it cannot run Xcode, compile the native iOS project, manage Apple certificates and provisioning, upload builds to TestFlight, or submit them to the App Store without access to a Mac.
NoMac gives Claude Code that missing Mac-side pipeline through MCP or CLI. So Claude still writes and fixes the app on your PC, while NoMac builds, signs, uploads, and publishes it in the cloud.
Gary, needing one particular machine just to get an app out the door has always felt like a silly gate. Knocking that barrier down so more people can actually ship their ideas is lovely to see.
Does the App Store rejection feedback make it back to the agent through the MCP, or is that where a human takes over? Review is the one step in the pipeline that stays human on Apple's side, so I wondered where the loop closes. Congrats on the launch, Gary.
NoMac.app
@vollos Yes, the agent can poll the the submission status and get back the whole feedback, so ready to act without human action!
@gary_miklos Nice, so the loop does close. An agent that reads Apple's rejection notes and ships the fix itself, didn't expect that to work already. Hope the numbers keep climbing today.
the no-xcode pipeline feels like it was built by people who actually shipped an iOS app from Linux and got tired of the friction. love that the MCP integration is first-class instead of an afterthought.
the "agent reads the rejection and ships the fix itself, no human action" answer is the part that would make me pause, not the no-Mac angle. Apple's review process assumes a person is accountable for what gets resubmitted, and repeated automated resubmissions after a rejection is the kind of pattern that gets developer accounts flagged regardless of how good the fix is. also curious where Apple Developer certificates and provisioning keys actually live in this pipeline, since that's the credential an agent would need custody of to sign and submit builds on its own
That credential-custody point is what I'd want documented before trying this. It would help to know how signing keys are scoped and rotated, who can trigger a resubmission, and whether a human approval gate can be inserted after a rejection.
Interesting product, but don't know how to implement it.
Given that iOS applications require a Mac and Apple’s own development software to build, then how is this actually creating a signed application without a Mac? Is the company using some kind of cloud based Mac or something else completely?
NoMac.app
@saksham_salvi Yes, we are using multiple cloud Macs.
code signing is usually the part that breaks headless iOS pipelines, certs and provisioning profiles expiring or getting revoked with no local Xcode to just click through the fix. how does NoMac handle that when a cert needs renewing, does the agent walk you through it or does it need a human to hop into the Apple Developer portal at that point
Interesting infrastructure play.
I'm curious—do you see AI agents becoming the primary users of app publishing pipelines, or is this mainly about making developers dramatically faster?