What actually needs a Mac in 2026
An honest inventory of iOS shipping in 2026: what genuinely requires Apple hardware, what only requires a human, and what a cloud pipeline can do on its own. Including the four things nobody can automate away.
· 6 min read
“You need a Mac to ship an iOS app” is half true, and the half that is false is the expensive half. What actually needs to happen on macOS is compiling and signing. That is it. Everything else people assume needs a Mac — TestFlight, metadata, screenshots, the submission itself — is a web API that runs anywhere.
So the real question is not whether you own a Mac. It is who runs the twenty minutes of macOS your app needs per release, and what it costs you to get there.
The four things a human still has to do
Apple gates these behind a person on purpose. No service can do them for you, and any service claiming otherwise is either misrepresenting or setting you up for a 4.2.6 rejection.
- ·Enrol in the Apple Developer Program. $99 a year, paid to Apple, with an identity check. No Mac required — it is a web form and sometimes a phone call.
- ·Create an App Store Connect API key. One page in App Store Connect, one download, once. This is the credential that lets a pipeline act for you, and it is revocable at any time.
- ·Answer the App Privacy questions. A short questionnaire about what your app collects, required before the first release. Nobody else can truthfully answer it.
- ·Accept the TestFlight invite on your phone. One tap. Then every build after that arrives on its own.
Four things, once, and none of them need Apple hardware. What people mean when they say they cannot ship without a Mac is almost never this list.
What genuinely needs macOS
- ·Compiling.Xcode and the iOS SDK run on macOS only, and Apple's licence keeps it that way.
- ·Signing and packaging. The certificate and provisioning dance that turns a build into an installable
.ipa. - ·Simulators. Same reason: they are part of Xcode.
Three items, all machine work, none of them requiring the machine to be yours. Which is the whole idea behind cloud Macs: rent the twenty minutes, skip the two thousand euros.
What needs nothing special at all
- ·TestFlight distribution — App Store Connect is a website, and the API behind it is open.
- ·Metadata, descriptions, keywords, screenshots and their upload.
- ·The submission itself, and the review status you refresh too often afterwards.
- ·Crash reports and tester feedback coming back out.
Your options, honestly
Buy a Mac. A Mac mini is the cheapest real one. It works, it never argues, and it is idle 99% of the time. If you are already an iOS developer this is a solved problem and you are not reading this post.
Rent a remote Mac. MacStadium, MacinCloud and friends. You get a whole machine, which means you also get to maintain a whole machine: Xcode updates, certificate expiry, disk space at midnight.
Use CI. GitHub Actions macOS runners, Codemagic, Bitrise, Xcode Cloud. This is the professional answer and it is genuinely good — if you are comfortable with YAML, Fastlane, and keeping signing assets in a secret store. The learning curve is the price, and for a first app it is steeper than writing the app was.
Use a pipeline that an agent can drive. Which is what we built, so read this with the appropriate suspicion: NoMac takes a project, builds it signed on a cloud Mac, pushes it to TestFlight in about three minutes, and submits it to review — over a CLI, an API, or MCP tools your coding agent calls itself.
npx @nomac/cli login # device code, approved in your browser npx @nomac/cli push # upload the project npx @nomac/cli build # signed release build on a cloud Mac
The honest limitation: you still need a real iPhone to look at the thing. Cloud simulators your agent can drive are coming; until then, TestFlight on your own phone is the loop, and you are the simulator. Anyone promising a fully hands-off path from prompt to App Store is skipping the part where somebody has to care whether the app is any good.
The part nobody warns you about
Getting a build to TestFlight is a solved problem however you do it. Getting through review is not, and it is where first-time submissions actually die — metadata that contradicts the binary, a missing privacy manifest, a category Apple has explicitly closed. Budget your attention accordingly: the build is an afternoon, review readiness is the week. Why App Review rejects AI-built apps covers what that actually looks like.
If you want the machine part to stop being your problem, point your agent at nomac.app/install and it will set itself up, or read the CLI reference and do it by hand.