When I got my first App Store rejection while building Hubbit: AI Habit Tracker, I spent three da...When I got my first App Store rejection while building Hubbit: AI Habit Tracker, I spent three da...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
When I got my first App Store rejection while building Hubbit: AI Habit Tracker, I spent three days convinced Apple hated my app.
They didn't. I'd just misread the rejection.
The mistake is treating the message as a verdict. It isn't. It's a specific guideline number and a reviewer who spent maybe four minutes in your app. Most of the time they're pointing at one screen, one permission string, one thing you can fix in an hour.
What actually works: Read the guideline they cite, not the summary. Reply in the Resolution Center and ask what specifically failed if it's vague. They answer. Fix the one thing. Resubmit.
Three days of panic, forty minutes of actual work.
If you're sitting on a rejection right now and haven't replied because you're intimidated: reply. They're not your enemy; they're a queue.
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started