Android%20A  w630 - Android: Google reveals what an application must avoid to stay on its Play Store

Notice to developers of mobile applications on Android. Google has just unveiled the four main reasons that could push the American giant to suspend an application from its Google Play store. Not to mention uploading a course designed to teach developers how to avoid being kicked out of their app store.

Deleting apps makes life difficult for developers
applications, which is why Google has highlighted the common "mistakes"
that developers commit, in order to help them prevent their
accounts are blocked by the big guardian. Google has published its
recommendations on the occasion of the publication of its new policy
program for developers, which came into effect on 21
October.

Applications with buttons and menus that link to pages
outside the Play Store are of particular concern. These links
refer either to applications from the same developer or to other
applications which may be affiliated with the developer, but which are not
not clearly labeled as ads or links
promotional.

A rich application store

"Without this clarity, applications can be suspected of
contain deceptive or disguised advertising. One of the ways
to avoid such errors is to point them out explicitly by
labeling buttons and links as "More apps", "More
of games "," Explore "," Discover our other applications "", alert
Andrew Ahn, product manager for Google Play App Safety. Google
communicates this advice on the assumption that developers do not
are making mistakes that violate its rules rather than engaging in malicious practices.

In addition to these disguised links, Google also resents abusive keywords, which allow developers to further showcase their application in the heavily stocked Android store, which would count according to Statista 2.7
million applications, compared to 1.8 million applications on the Apple AppStore.
Text blocks and lists with repetitive descriptions
or words unrelated to the application violate the policy of
listing and promoting Google stores.

“Writing a clear description of the application, intended and optimized for readability and user understanding, is one of the best ways to avoid this violation,” says Andrew Ahn.

Google launches online course

Besides these two violations, this one also points to the issue that some of the 2.7 million Android apps on the Play Store are broken because the developers abandoned them. This creates problems for Android Play Store users, and developers run the risk of violating Google's "minimum functionality policy", which could affect their developer account with Google and therefore other apps made by the manufacturer. of the application.

"To mitigate the negative impact on the reputation of the developer and on the application of the application, we must consider the non-publication of these applications from the Play Store," writes the head of Google. Google also doesn't approve of app proposals that are just app repackaged websites, as most of them are just designed to drive traffic to a website rather than giving Android users a reason to use an app.

Google considers them to be "WebView spam" and removes them. WebView allows developers to view web content in an application. Rather, developers should think about how an app can deliver something better than what's already available on a website. To help developers understand the difference between a useful app and an app that just mimics a website, Google has posted a "Webview Spam" course on Play Academy.

This course promises to teach application developers to align application behavior with Google Play's spam policy WebView, to distinguish between examples of acceptable and unauthorized behavior of applications regarding spam WebView, and to avoid WebView spam in applications.

Source: ZDNet.com

(function(d, s, id) { var js, fjs = d.getElementsByTagName(s)(0); if (d.getElementById(id)) return; js = d.createElement(s); js.id = id; js.src = "http://connect.facebook.net/fr_FR/all.js#appId=243265768935&xfbml=1"; fjs.parentNode.insertBefore(js, fjs); }(document, 'script', 'facebook-jssdk'));