App Store Review & Rejection Recovery Consulting
Apps launched across consumer, medical, and intimate wellness categories. My guideline readings track what App Review enforces in practice, which often diverges from the written document. Rejection recovery, pre-submission audits, and grey-zone categories.
- grey-zone categories: intimate wellness, regulated health, reputationally sensitive content
- rejection recovery within the 14-day response window
- reviewer notes that turn a 3-round rejection loop into a first-pass approval
Related work
Apple's Problem with Bodies
I shipped a wellbeing journal and discovered the App Store still isn’t sure whether the human body is health, lifestyle, or sin.
Read the article →
Silk
The health metric your phone doesn't track
See the project →
Epsy
Health companion app for epilepsy patients.
See the project →
Murmur
Practice difficult phone calls with AI. Build confidence, reduce anxiety.
See the project →What clients say
"Vadim was instrumental to the success Epsy enjoyed on iOS, taking it from an idea on a Miro board to the highest rated and most downloaded app of its kind on the store."
James C. · Mobile Engineering Lead, Epsy
"We had a strict deadline, and Vadim managed to complete the job in time. He gave us meaningful feedback and suggested better approaches, not trying to blindly stick to our specification."
Founder · Pre-seed streaming service
"I can say with confidence that it will be difficult to find a better developer. Vadim is achievement-oriented, highly organized, with very good communication skills."
Alex Z. · Co-Founder, eda.so
Common engagements
Pre-submission audit
Half-day to one-day review of a build before you submit. I map every likely objection to a specific guideline, predict the reviewer's two-minute path through your app, and tell you what to change. Saves you a round of rejection and a two-week clock.
Rejection recovery
You've been rejected and the clock is 14 days. I read the rejection, identify the guideline driving it (often not the one cited), and prepare the response and binary update.
Write your reviewer notes
The most under-used artefact in submission. A good set turns a 3-round rejection loop into first-pass approval.
Areas I cover
Pricing
Architecture reviews, hiring help, second opinions on that thing that's been bugging you.
Available nowFeatures, MVPs, migrations, firefighting. Minimum 5 days.
Available nowPriority support: review agency code, join architecture calls, catch problems before they ship.
Questions
Will you help me submit an app that violates the guidelines?
No. If the app is in breach, the fix is changing the app. Working around the guideline stops being an option once a reviewer has flagged it. I'll tell you which category your build falls into and what needs to change before submission.
Can you guarantee approval?
No. Nobody can. What I can guarantee is that you'll go into the submission with the objections pre-answered, the reviewer notes written, and a recovery plan if the first round doesn't pass.
What if we've been rejected multiple times already?
That's the most common entry point. Send me the rejection history and the current metadata. A one-day review usually surfaces the pattern. It's almost always the same underlying issue rephrased as different guideline citations.
How do I get a quote?
Two paths. If you need speed, send me a detailed brief and I'll quote from it (usually within 48 hours). If you'd rather talk first, book a free 30-minute scoping call and I'll quote after. Most clients who pick the brief path land on the call anyway once we get into the specifics, but the door is open either way.
How quickly can you start?
Advisory calls can happen within days. For project work, I typically need 1-2 weeks notice to clear the calendar, though I keep some buffer for urgent firefighting. Check the availability badges above for current openings.
Do you work with early-stage startups?
Yes, from pre-seed to Series C and beyond. For very early teams, the advisory tier often makes more sense than project work: you get architecture guidance without committing to a large engagement before you've validated the product.
What's included in the day rate?
Everything: code, architecture decisions, code review, documentation, async Slack availability during working hours. No surprise add-ons. I bill for time spent working on your project, not for "thinking about it in the shower."
How do you handle timezone differences?
Currently in Vancouver (PST) with full overlap for North American teams. For UK and Europe, I'm online by their afternoon. For Gulf or APAC, we'd agree on overlap hours and handle the rest async. I've worked with teams from San Francisco to Dubai.
Where I've worked CV · LinkedIn
Stuck in App Review?
Describe what you're working on, or book a free 30-min scoping call. I reply within 48 hours.
work@drobinin.com Book a free call →