Publish to the stores
Apps are distributed on App Store and Google Play. This page brings together the accounts involved and the process for each release.
Which accounts are involved
Section titled “Which accounts are involved”Apple. An Apple Developer Program account, with access to App Store Connect to manage the listing, the binaries and the versions.
Google. A Google Play Console account.
Ownership and access
Section titled “Ownership and access”The App Store and Google Play accounts belong to the customer. The app listing, the reviews, the metrics and the assets associated with those accounts are theirs.
The access Reskyt needs in order to build, submit and maintain the app is defined at the start of the project. Accounts and access are best resolved in the early phases, because they condition the launch schedule.
Talk to your contact at Reskyt to settle the details for your case.
Who does what
Section titled “Who does what”Submitting the binary and the technical side of the review are handled by Reskyt. The store listing and the business decisions belong to the customer.
Every new version goes through store review. The timeframes are set by Apple and Google.
Checklist before submitting for review
Section titled “Checklist before submitting for review”- Privacy policy published and reachable from the app.
- Store listing: name, description, screenshots, icon.
- Each store’s data privacy questionnaire completed.
- Purchase flow tested end to end on a release build.
- Update modal with the version numbers updated.
Updates
Section titled “Updates”When you publish a new version, you have to update the version numbers in the update modal. If you do not, users on older versions will not see the notice.
Keeping the accounts up to date
Section titled “Keeping the accounts up to date”Developer accounts are renewed periodically according to the terms of each store. It is worth identifying who tracks that inside the customer’s organisation, since an expired account affects the app’s presence.