Moving apps

TL;DR This article fills in some of the gaps in the official docs and add rationale to why you should consider moving your app to a non-human Google account.

Google offers the ability to move/transfer one of many apps from one Google account to another. But before you transfer highly recommend reading the official docs on how to transfer apps to a different developer account here.

Why transfer?

Are you using your personal Google account for apps?

If your app(s) are associated with your personal Google account you run the risk of having your access to Gmail, Google Photos, Drive blocked if Google Play account is suspended due to a breach of Play content policy. The thought of losing access to my emails, family photos is a very frightening prospect. You might think you’ll never be in breach and maybe you’re right? but remember the Play content policy is frequently updated and you have to ask yourself how closely you read the updates. I ran into policy breaches a few times and none of the apps I’ve released are particularly risky. The first app that I wrote to get my first Android job was a wallpaper changer based geotagged Flickr photos and user’s location. It was pulled due to copyright infringement (I mistakenly used Flickr’s logo and name). So certainly worth considering moving them to seperate Google account.

 

What if the account owner leaves your organisation?

Recently at work the first Android developer left for greener pastures. I mention first because he was only one in the Android team and registered his work Google account as the Google Play Developer owner which I’m sure happens a lot. When he left the company a few weeks ago his Google account was deactivated as you’d expect. However, because that account was the owner on Google Play we *lost* all access to Google Play console 😱😱😱. Thankfully we were able to restore their Google account which restored our access. But keeping an ex-employee’s account active just for this would be less than ideal.

Continue reading