Skip the App Store: Why a PWA Might Be the Smarter Launch

You spend three months and a serious chunk of budget building an iOS app. You submit it to Apple. Four days later, you get a rejection email that quotes a guideline number you've never heard of and gives you almost no useful detail on what to actually fix.

You resubmit. You wait again.

If that sounds familiar, you're not unlucky. You're just going through what most app teams go through.

According to Apple's own 2025 App Store Transparency Report, Apple reviewed 9,100,620 app submissions and rejected 2,093,244 of them, roughly one in four. And the breakdown of why is telling. Performance problems accounted for 1,354,418 rejections on their own, more than legal, design, business, and safety issues combined. Legal and privacy concerns caused another 495,673 rejections, design issues 415,532, and business or monetization rules 283,820. You can see the full breakdown in Apple's transparency report itself. appleapple

Here's the part that stings most: 387,087 of those rejected submissions were eventually approved after a resubmission. In other words, a huge share of "rejections" aren't apps that were fundamentally broken. They're apps that got bounced over something fixable, sent back into a queue, and made to wait through the review process a second time. Sometimes a third.

That's not really a flaw in your product. It's just the cost of building for a platform where a human or an algorithm you'll never meet decides, on their own schedule, whether your work gets to exist.

What you're actually signing up for

The rejection risk is only part of the story. Publishing a native iOS app comes with a whole layer of overhead that has nothing to do with whether your app is good.

You need an Apple Developer account, which costs $99 a year and renews forever, whether you ship updates or not. You need a Mac to build and submit the app in the first place; it's not optional, not negotiable. You need separate codebases (or at least separate build pipelines) for iOS and Android, because "write once, run everywhere" has never fully been true for native apps. Every update, even a one-line bug fix, goes back through the same review process that just took four days the first time. And your screenshots, your privacy policy, your support links, your test account credentials- all of it has to be exactly right, or you're back in the queue.