The review · Pre-submission
Test my app before submission.
Your app is ready. You are about to hit "Submit" and wait 48 hours for a reviewer's verdict. We run it through Apple's and Google's known rejection reasons first, so you submit an app that passes on the first try.
Written feedback within 7 working days · Request your quote, quick reply with a precise price, no surprises.
The checklist
We check what the reviewers check.
On the app side
- Stability: first launch, backgrounding, resume, rotation, on several real devices. The crash on launch is the dumbest and most common rejection reason.
- The demo account: present, working, with real content in it. A broken demo login is an automatic rejection.
- In-app purchases: a compliant paywall, purchase restoration, the mandatory disclosures, the subscription management button.
- Permissions: every request justified by a clear message, no unnecessary permissions, account deletion within reach.
On the listing and paperwork side
- Privacy: the App Store Connect questionnaire and the Play listing consistent with what the app actually collects, the policy online and up to date.
- Screenshots and the listing: the right formats, screenshots that show the real app, copy without forbidden promises.
- The age questionnaire and the metadata that triggers requests for justification.
- The Google Play traps: the mandatory testers, the data safety declarations, the signing key.
What you get
Written feedback, point by point, within 7 working days.
For every issue found: the rejection reason it maps to, the exact Apple or Google rule involved, and the fix to make before you submit. For ambiguous points, the wording to have ready if the reviewer asks the question.
- The list of blockers: what will get you rejected, to fix first
- The list of risks: what often passes but can snag, with the counter
- A written green light when it is ready: you submit with confidence
What it is not
- A guarantee of acceptance: nobody can give one, Apple alone decides. Anyone who promises it is lying to you.
- A full UX or security audit: for that, there is the mobile app audit.
- A submission done for you: we can do that too, but it is a separate service, mention it in your message.
We would rather tell you what the offer does not cover before you pay, not after.
How it works
Three steps before you hit "Submit".
Step 1
You write to us
TestFlight access or an APK, plus your listing and screenshot drafts if you have them. A precise quote, no surprises, sent quickly.
Step 2
We run the app through the checklist
On real iOS and Android devices, with the list of rejection reasons in hand, like a reviewer in a hurry on a Monday morning.
Step 3
You fix, then you submit
The written feedback arrives within 7 working days. You fix the blockers, and you submit an app that has already been through its review once.
Questions
Before you decide.
My app has already been rejected: is it too late?
Quite the opposite, it is the best time. Send the rejection message with your request: we decode the reason, check that your planned fix is enough, and go through the rest to avoid a second rejection on a different point.
Apple only, Google only, or both?
Your call. The two stores have different rules and different traps: the quote clearly separates the two, and you choose.
7 working days is too long for me.
Say so in your message: if the schedule allows it, an accelerated review is possible and the quote will say so. We never promise a deadline we cannot keep.
Do you submit on my behalf?
We can, as a separate service: preparing the paperwork, the screenshots, the submission and the review follow-up all the way to "Ready for Sale". Mention it in your request and the quote will cover both.
Ready to submit? Let's check first.
Send access to your app and the submission date you are aiming for. Request your quote, quick reply with a precise price, no surprises.