Shipping
Find out before review does
A rejection costs a week and tells you one thing at a time. Memberside checks your app against what each store actually enforces, reading the app you built rather than a form you filled in.
Free while in beta. No credit card needed.
The audit
Three answers, and only one of them is urgent
Every check says what it means and what to do about it. The point is to spend your attention on the handful of things that would actually stop you.
Block
This one stops you
The store will refuse the submission, or reject the build. No screens placed, a listing field over the limit, no app icon, no way for the reviewer to sign in, member content with no way to block anyone, or an app that creates accounts and cannot delete them.
Warn
Review is going to ask
Not fatal, but you want an answer ready in the notes. An app name that reads as promotional, screens locked behind a role your demo account does not have, or a shop whose digital goods have not been classified.
Pass
Evidence you can point at
Listed rather than hidden, because "members delete their own account from the Delete tab" is the exact sentence that answers guideline 5.1.1(v) — and it is more use in front of you than filed away.
The audit as it scored a demo app, before its listing was filled in.
Why it reads your app
Some rules are not settings
Three of the obligations most likely to sink a community app are satisfied by a screen being in your app, and by nothing else. No field turns them on, and no wording in the review notes stands in for them.
Guideline 1.2
Reporting objectionable content
Comes from News Feed, Create Social Post or Photos, whose posts and photos carry a Report action. BuddyPress Activity has no report action at all — an app built on it alone has user-generated content and no way to flag any of it.
Guideline 1.2
Blocking an abusive member
Comes from User Blocking, which every app with member content gets automatically — a feed, chat, forums, groups or a directory brings it along. Members block from the ⋯ menu on a post, comment, profile or conversation, and the two disappear from each other everywhere. An app that has member content and no User Blocking fails the audit, with the feature offered as the fix.
Guideline 5.1.1(v)
Deleting your own account
Comes from the Settings screen, confirmed with the member’s password. Apple explicitly rejects a link to a web form or an email address, so there is nothing you can write in the notes that saves it.
A checklist cannot tell you this. It is why the audit walks your navigation instead of asking you to confirm things about it.
What is in it
Everything the stores ask for, in one place
The readiness audit
Listing metadata, per store
Notes for App Review
Screenshots of the real app
A folder fastlane can upload
Your listing, your account
Being straight with you
You press submit, and that is deliberate
App Store guideline 4.2.6 does not allow an app-generation service to submit on a client’s behalf. Apps built from a template have to come from the developer account of the business they belong to — so the last step is yours, from your own account, with your own name on the listing.
We take it as far as it can go: a folder laid out for fastlane, with the metadata, review notes and screenshots already in it. Then you upload.
Questions