Four App Store rejections and what they taught about shipping.

Four App Store rejections and what they taught about shipping.

I built six web apps over the last decade. Four of them hit the App Store. Three of those four got rejected on the first submission. The fourth one sailed through, which taught me more than the rejections did because I could actually see what I'd done differently.

The first rejection came back with a note about "unclear purpose." I'd built something I understood perfectly because I lived in it every day. The reviewer had thirty seconds and a feature list that read like someone solving their own problem, not anyone else's. I rewrote the app description to start with the problem the app solved, not the tool itself. The resubmission cleared.

The second one was about payment. I'd set up in-app purchases the way I thought made sense. Apple disagreed. The guidelines are specific about how you implement subscriptions, and I'd skipped a step that seemed redundant. I thought I was being efficient. Apple thought I was being incomplete. Adding that step took two hours. It was the kind of thing that would have been obvious if I'd read the docs instead of skimmed them.

The third rejection stung because it wasn't about functionality. It was about imagery. I'd used a screenshot that included an interface element from another app. Not intentionally. Just screenshot overlap. The reviewer caught it. I thought it was invisible. It wasn't. That one taught me the difference between what you see when you build something and what a stranger sees when they look at it fresh.

The fourth app didn't get rejected. I'd learned by then what "clear" meant to someone else. Clear isn't clever. Clear isn't what makes sense to you. Clear is what makes sense to someone who's never seen your work and has no reason to care about it until you give them one.

Those rejections weren't failures. They were a conversation with the gatekeepers between your idea and the people who need it. Most of the time, they're right. Even when they feel arbitrary, they're usually protecting something real (app quality, user clarity, payment trust). Fighting them wastes time. Learning from them ships faster.