Publish on Google Play

Use the files from your dashboard to publish your app under your own Google Play developer account. On the Pro and Business plans, we upload each new version for you.

1. 1

   Create the app in Play Console

   Open Google Play Console, choose Create app, enter your app name and default language, and select App and Free.

2. 2

   Fill in the store listing

   Add the short and full description, then upload the icon (512 × 512), feature graphic (1024 × 500) and phone screenshots from your store assets.

3. 3

   Complete the app content section

   Add your privacy policy link, content rating, target audience and data safety answers. In data safety, declare that your app collects phone numbers for sign-in, and anything else your app asks for (name, email, city, orders).

   Your app also sends usage statistics to Yallapp (see Analytics). In the data safety form, declare under App activity: App interactions, In-app search history and Other actions; under Device or other IDs, the random install ID. For each: Collected, not shared (Yallapp processes it for you), processed ephemerally: no, optional (people can turn it off in the app's Settings), and the purpose Analytics. Data is encrypted in transit, and people can ask for deletion through you.

   For notifications, apps on Yallapp's hosted API keep each signed-in phone's push token, the language the app shows on it and the country it signs in from (worked out from the connection, the IP itself isn't kept), so you can send a campaign to the people who read a language or live in a country. Shops also get how many items each signed-in person has in their cart (not what), for the reminder of a cart left. Declare under Location: Approximate location, and under Device or other IDs: the push token. For each: Collected, not shared, required, for App functionality.

   Data safety also asks how people delete their account. They do it in the app (Account › Settings › Delete account); for the web link Google asks for, give your app's own page, where they can ask without the app: the Ready to submit? section on Publishing shows its address (/a/<app ID>/delete-account on yallapp.com.tr), and checks the rest of what the stores ask before you send the app.

   info

   Under App access, give reviewers your review phone number and fixed code: from the dashboard's App sign-in page, or, for apps on WordPress or their own API, the Store review account on Publishing (required before a build). Without it, reviewers can’t sign in and the app may be rejected.

4. 4

   Run a closed test

   Create a closed testing release and upload your .aab file. New personal developer accounts must run a closed test with enough testers for the required period before they can publish to production. Check the current requirement in Play Console.

5. 5

   Release to production

   Create a production release with the same .aab, add release notes and send it for review. Keep your signing key safe: every future update must be signed with it.

6. 6

   Pro and Business: let us upload

   In Google Cloud, create a service account for your Play Console's project and a JSON key for it (IAM › Service accounts › Keys). In Play Console, invite the service account's email under Users and permissions with access to your app's releases. Upload the JSON key on the Publishing step. We then upload every new build for you.