Checklist · free
App Store & Play Store submission checklist
A 34-point checklist for putting a branded event app on the App Store and Google Play, covering accounts, listing copy, screenshots, privacy forms, test access and review timing. Start two weeks before launch; store review can take days and rejections usually come from small, avoidable gaps.
No sign-up needed.
Who it is for
- Event agencies publishing apps under their own or a client account
- Corporate teams who must submit a branded app in a short window
- Project managers who track submissions across several clients
How to use it
- Decide first whose developer account will hold the listing: yours, the client or the vendor.
- Work down the list in order and record the date each item was completed.
- Submit to both stores at least ten days before the event, and plan a web fallback.
- Keep the review notes and test login in a shared folder so a resubmission is quick.
The contents
Accounts and ownership
- Decide who owns the listing and write it down
- Apple developer account active and renewal date noted
- Google Play developer account verified
- Legal name and address match on both stores
- Support email address that someone monitors
Listing content
- App name checked for clashes and character limits
- Subtitle and short description written
- Full description reflects the real features
- Keywords chosen for the App Store
- Category and age rating selected
- Promotional text for the launch week
Visual assets
- Icon at the required sizes with no transparency issues
- iPhone screenshots at required sizes
- Android phone screenshots
- Tablet screenshots if the app supports tablets
- Screenshots show the real app, not mock-ups
- Feature graphic for Play
Policy and privacy
- Privacy policy URL opens on a phone
- Apple privacy nutrition label completed
- Play data safety form completed
- Account deletion route described in the app or web
- Permissions requested are explained in plain text
- Notification permission prompt appears at a sensible moment
Review access
- Test login that works without an OTP to a real phone
- Review notes explain the occasion code or invite flow
- Contact number for the reviewer if needed
- Any region or date restriction explained
Release and after
- Choose manual release after approval
- Internal test build checked on a real device
- Submit at least ten days before the event
- Store link added to invitations and the web page
- Version number and build number recorded
- Plan for a hotfix build and who can submit it
Where it has been used
Informed by multi-client app work for agencies, where several apps shared a platform but each needed its own listing and review path.
Questions people ask
Which store takes longer?
Timing varies and neither store promises a date. Submit both early, and avoid scheduling anything critical, such as a press release, until the apps are visibly available to download.
Do we need our own developer accounts?
Not always, but listing ownership matters. If the app sits in the vendor account, agree what happens when the contract ends, and whether the listing can be transferred.
What commonly causes a rejection?
Missing test login details, a privacy policy link that does not open, and screenshots that do not show the real app. Fix those three and most first submissions pass without a second round.
Want this running inside your event app?
Sociana turns lists like this into live screens, requests and reminders for your guests and your desk. A 20-minute walkthrough shows how.