Google keeps changing the rules
Building a mobile app isn't just building a product. It's also surviving an ecosystem that keeps changing.
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 : apps that feel incomplete or contain non-finalized features are systematically rejected.
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 problem isn't launching "small". The problem is launching something unfinished.
Waiting two weeks sometimes avoids three months of damage
Sometimes waiting two extra weeks avoids massive damage : bad reviews, App Store rejections, lost credibility, fast uninstalls.
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 15-minute call to anticipate rejection reasons before submission.
