How to Prevent Application from getting Suspended from Google Play

Many Android developers would have faced suspension of their Android application(s) from Google Play. After spending enough time and money to write an application, App suspension from Google Play is the second worst thing to happen for a developer. The worst thing is, after multiple suspension, the Publisher account suspension. Many create another publisher account but face the axe again. Most of the time the suspension mail tells about the policy/clause which the app violated but not the exact issue which led to suspension leaving the developers clueless. So after seeing multiple suspension of peers’ application and accounts, I am trying to provide information on some reasons for suspensions so that new application developers are aware of these basic issues which we take lightly but proves costly later.

Why Apps get suspended in Google Play?

Whenever an app is published in Google Play, there is no manual approval process which validates that the app doesn’t violate any Google Play Policies. There are some basic automated checks done such as the minimum maturity level of the application based on the permissions mentioned in the manifest file or the application description. For example, if ACCESS_FINE_LOCATION permission is specified in the manifest file of the application, then minimum maturity level of the app should be “low maturity”. Maturity level “Everyone” is not available for the app. Similarly, if the app description or screen shot contains graphic content (in case of apps like scare your friends, scary pics, etc), then the minimum maturity level for the app should be “Medium Maturity”. The Publisher site will enforce this by either disabling (blurring) the option making it unavailable in the Maturity Level drop down or by raising the maturity level of your app forcefully after your app is published.

Since there are no manual approval process, the published application will be available for download within hours after publishing. The advantage of this is that the developers can see the response to their application instantly. Developers can view crash reports in the publisher account and if they find any critical issues with the app, it can be resolved and released within hours to their customers.

The problem is that the application will be checked for any violation “later” and if Google finds any violation, the app is suspended.

When will the application be checked for violation?

There is no official policy on when an app will be checked for violation. From my observation, the app are checked for violation during the following

• When the app goes to the Trending App list for the first time. App goes into Trending List when there is significant increase in the app download. The Trending App list can be found in the Google Play app on your Android phone or in https://play.google.com (https://play.google.com/store/apps/collection/movers_shakers?hl=en)

• Whenever someone raises an objection. Objection can be raised by choosing the “Flag as Inappropriate” option in the Google Play app against an app or from this link https://support.google.com/googleplay/android-developer/answer/1085703

Common reasons for app suspension!

Guidelines which if violated will result in app suspension are listed at Google’s Developer Program Policies page (https://play.google.com/about/developer-content-policy.html). However, some of these are at very high level and we discover the reasons for app suspension only after our apps get suspended. So here are some of the common reasons for app suspension.
 

Copyright issues

Don’t just search and get images from Google Images and use it in your app. If the copyright owner of the image raises objection to your app it will obviously be suspended. Instead, search in Google image search with proper Usage Rights option selected (In Search Tools->Usage Rights) and use only those images whose copyrights you don’t violate.

      External URL calls from background

      Whenever your application makes a URL call without an activity of your application in the foreground, do make sure that you notify the user of the device in the notification bar. Any external URL calls when the application is not in foreground is seen suspiciously and the app can be marked as a spam or spy app. Also, there should not be any option to disable the notification.

      Interstitial Ads only when the activity is in foreground

      If your app displays interstitial ads (or any other ads for that matter), make sure the ads are not displayed when the app is in background or exited. For example, when your app is interrupted by a phone call the app goes into background. At this point of time if you display an interstitial ad thinking your activity is alive (but paused) it will be violating the ad policy and may result in suspension of your app.

      Excessive keywords or incorrect app description

      In detailed description section for your app in Google Play Publisher console, avoid putting more than 3 to 4 keywords and the app description should match the working of the app.

The reasons are not exhaustive and if you have more points to add to the list, please mention in the comment section.

Read Policy Updates carefully

Whenever there is a Google Play Developer policy update, do read it carefully since they usually come with new restrictions which may lead to suspension of your app even if it had been in Trending List. Not only your app, you should also update any third party libraries that you are using in your app which released updates to be in compliance with the latest policy updates.

What next after an app is suspended?

I wish no hard working developer faces this, but in case one of your app is suspended and you feel the app was suspended by mistake then you can file an appeal at https://support.google.com/googleplay/android-developer/answer/2477981?hl=en

If the app suspension is not revoked even after an appeal and you know the reason of suspension then you have an option of correcting the mistake and publishing the app again (with a different package name, of course). But I suggest not to - because multiple suspension will result in publisher account suspension. Instead, create another publisher account and upload the modified application or any other application that you want to publish to the new publisher account.

Disclaimer

Some of the observations above are from my experience and interactions with other Android developers. If your observations are different from mine would like to hear from you.