Specification 04
Store publishing
Help getting into the App Store and Google Play: from developer account to answering a review rejection.
04.1
What you receive
| Deliverable | Contents |
|---|---|
| Readiness checklist | Signing, versions, icons, screenshots per size |
| Bilingual metadata | Name, description, keywords within character limits |
| Data declarations | App Privacy and Data safety matching actual behaviour |
| Privacy policy | Structure and check against the app |
| Review support | Analysing feedback and preparing a reply or fix |
04.2
Quality criteria
- Data declarations match the real SDKs in the build
- Android target API meets the current Google Play requirement
- Test account and reviewer notes included
- The developer account belongs to the client, not us
04.3
Common rejection reasons
- Incomplete or inaccurate data collection declaration
- No test access for the reviewer
- Sign-in features without a way to delete the account
- Metadata promising features the app lacks
04.4
Scope boundaries
We prepare materials and help with the process. Approval is decided by Apple and Google — nobody can guarantee it, and we do not promise it.
Store publishing
Tell us the context — we will reply with questions and a first step.
Discuss a task