Apple rejects "almost done"

There's a huge difference between a simple V1… and an unfinished app. And Apple sees it immediately.

Many projects want to publish fast. Which is understandable. There are deadlines, pressure, sometimes investors, sometimes limited budgets. So the idea becomes : "Let's publish now, we'll fix it later."

The problem: Apple hates "almost ready"

An empty screen ? Reject. A button opening an incomplete page ? Reject. "Coming Soon" features everywhere ? Reject. A broken flow after signup ? Reject.

Because Apple looks at what the user will experience today. Not what'll be ready in three weeks.

The App Store Review Guidelines (section 2.1) are explicit. Apple's own wording : "Submissions to App Review […] should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission." (Apple App Store Review Guidelines 2.1, 2026). The guideline ends just as plainly : "We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems."

The most important thing to understand is what a rejection actually costs you. Apple states that 90% of submissions are reviewed in less than 24 hours (Apple App Review, 2026). So a clean submission is usually approved the next day — but each rejection sends you back to the end of that queue, and a fix-plus-resubmit cycle routinely turns a 1-day wait into a 4 or 5-day one.

First impression is extremely brutal

Imagine downloading an app… and immediately landing on unusable functions, empty screens, incomplete menus, interrupted flows.

The product impression turns catastrophic fast. And on mobile, the first impression is extremely brutal. The user opens. Tests for a few seconds. And immediately decides whether the experience feels serious or not.

A coherent V1, not an empty V1

That's also why a smart V1 isn't necessarily a tiny app. It's mainly a coherent app. An app that :

• works well,
• stays stable,
• delivers a clear experience,
• avoids obvious frustrations.

The key difference is scope versus finish : the problem isn't launching "small", it is launching something unfinished. A 3-screen app where all 3 screens work is a V1. A 12-screen app where 4 are placeholders is a rejection.

Waiting two weeks sometimes avoids three months of damage

In short : waiting two extra weeks avoids massive damage — bad reviews, App Store rejections, lost credibility, fast uninstalls. Two weeks of polish against three rejection cycles of 4 days each, plus the 1-star reviews that arrive in week one and stay on your listing for years, is not a close call.

A successful V1 doesn't try to do everything. It mainly tries to do the essentials well.

Is your app "almost ready" or actually ready to be judged by Apple ? Book a 30-minute call to anticipate rejection reasons before submission.