Calda

Google Play Console

Set up access so we can publish your Android app to internal testing and the Play Store.


Why we need this

The Google Play Console is where Android apps are uploaded, tested, and published. Calda needs a role on your developer account so we can manage releases, store listings, and signing keys.

Like all other accounts, this one should be owned by you. Your app's identity, store listing, and publishing history live under this account, so keeping it under your company means that history and ownership belong to you, not us.

Do I need a credit card?

Yes. Google Play requires a one-time $25 USD registration fee to create a developer account, and you'll need a payment method to pay it. Unlike Apple, this is a single payment — there's no annual renewal.

Identity verification can delay you

Google rolled out additional identity verification for developer accounts. Organization accounts now require a D-U-N-S Number, and Google may ask for a government ID or business documentation. Verification can take up to 48 hours, so start this early so enrollment isn't blocked.

Step-by-step setup

Register a Google Play developer account

Go to play.google.com/console and sign in with the Google account that will own the account. Choose Organization or Personal, then pay the one-time $25 USD registration fee.

Complete identity verification

Upload a government ID or business documentation if Google requests it. Verification can take up to 48 hours.

Fill in the developer profile

Once approved, open the Play Console and complete the Developer profile section.

Invite Calda

In the Play Console, go to Users and permissions and click Invite new users. Enter the email we share with you and assign the Admin role — or a custom role with at least:

  • Release manager
  • Store listing editor
  • App access for all apps we'll be working on

Set the access expiry to No expiry unless you want to rotate manually.

Confirm in Slack

Don't forget to notify us in Slack so we can accept the invitation and confirm that we can sign in and see the account.

Conclusion

That is it — once you've granted access and confirmed in Slack, we'll handle the rest of the publishing setup on our side.

How is this guide?

On this page