64% of the apps Apple rejects fail for the same reason. Do you know what it is?
Two-thirds of the apps rejected from the App Store fail on performance. What quality means on iOS and how to build it in from day one.
In 2023, Apple reviewed 1.76 million apps for the App Store. It rejected almost two-thirds of them for a single reason: performance. Not poor design, not privacy issues. Performance. An app that freezes, that burns through the battery like an oven, that takes four seconds to open a screen that should open in a fraction of one.
That's not just a statistic. It's Apple stating plainly what kind of software it wants in its ecosystem.
What “quality” means in iOS development
Quality is one of those words everyone uses and nobody defines. In the context of building apps for Apple platforms, it has a very concrete meaning: a quality app does exactly what it promises, without the user having to think about how, and does it just as well on an iPhone 16 Pro as on an iPhone 13 Mini at 20% battery with five apps open in the background.
Let me be clear: quality isn't a layer you add at the end. It isn't the moment you “polish” the app before sending it to review. It's a decision you make on the first line of code, and it shows up in every architecture choice, every network call, every screen transition.
And here's the real problem: nobody tells you this when you start. Nobody warns you that an architecture you got wrong in the first week turns into technical debt you'll be paying off for years. That a main thread blocked for 16 milliseconds is noticeable. That users don't know why the app “feels heavy,” but they feel it, and they uninstall.
The 17% rejected for design says more than it seems
Back to the data. 17% rejected for design. At first glance that looks small, but you have to understand what “rejected for design” means in Apple's criteria: interfaces that don't follow the Human Interface Guidelines, confusing navigation, elements that don't respond to touch the way you'd expect, text that's unreadable in real-world lighting.
Design, here, isn't about whether the colors are pretty. It's about whether the app respects the user's mental models. Whether there's a button where the user expects a button. Whether the navigation follows a logic that someone who has never seen the app can figure out in under ten seconds.
Apple has spent decades building those expectations into its users. When your app breaks them, even slightly, users sense something is off even if they can't say exactly what. And that feeling is hard to overcome with any number of new features.
The culture of quality that sets the Apple ecosystem apart
There's a reason a well-built iOS app takes longer to develop than an equivalent one for other platforms. It isn't inefficiency. It's the standard.
Apple has created an expectation of polish in its users that doesn't exist in the same way in any other ecosystem. That expectation is at once the developer's toughest demand and their biggest competitive advantage. Because if you manage to build something that meets that bar, you have something users will want to pay for.
At AC Academy we've spent years watching the difference between developers who understand this from the start and those who find out late. The first group builds with care from the first commit. The second spends the last months of development trying to repair decisions they made before they understood the consequences.
Quality isn't the end goal of development. It's the starting condition.
What to do with this
If you're building an app right now, or learning how to, keep these three principles close:
The main thread is sacred. Never do heavy work on the main thread. Anything that might take more than a few milliseconds goes to the background, with concurrency. If you're not yet comfortable with async/await in Swift, that's the first thing to fix.
Measure before you optimize. Instruments exists for a reason. Run the Time Profiler before deciding something “is slow.” The bottleneck is almost never where you think it is.
Design doesn't start in Figma. It starts in Apple's Human Interface Guidelines. They're public, they're up to date, and they're the most valuable document an iOS developer can read before opening Figma.
The 64% rejected for performance isn't a technical skills problem. It's a culture problem. And culture is built from day one.