Publish to the Google Play Store

Mar 8 2022 · Kotlin 1.5, Android 12, Android Studio Arctic Fox | 2020.3.1

Part 1: Publish to the Google Play Store

06. Best Practices for Google Play Store Listing - Part 1

Episode complete

Play next episode

About this episode
Leave a rating/review
See forum comments
Cinema mode Mark complete Download course materials
Previous episode: 05. What’s New in Google Play Console Next episode: 07. Best Practices for Google Play Store Listing - Part 2

Get immediate access to this and 4,000+ other videos and books.

Take your career further with a Kodeco Personal Plan. With unlimited access to over 40+ books and 4,000+ professional videos in a single subscription, it's simply the best investment you can make in your development career.

Learn more Already a subscriber? Sign in.

Notes: 06. Best Practices for Google Play Store Listing - Part 1

Google Play Store Listing Certificate

Developer Policy Center

Heads up... You've reached locked video content where the transcript will be shown as obfuscated text.

Your app store listing is critical to make a lasting impression with users and key to your apps discovery on Google Play store. This is part one of best practices episode, where you will learn how to comply with Google place store listing policies. You'll also learn best practices for text, that is developer name, app title and descriptions. You'll see Google Play store listing policies first. For a complete list of Google Play store listing policies, you can refer to Developer Policy Center link in the resources for this episode. It includes policies around several categories. Let's look at few of them. Deception. This category sees, don't use false or misleading information to describe your app. Also, don't misinterpret your app with graphic assets that do not accurately or clearly depict its functionality. Don't improperly categorize your app. Now let's look at policies around impersonation. Don't use another app or entity's title or name in the manner that may result in misleading users. Don't imply endorsement or relationship with another entity where none exist. Don't use graphic assets that are identical or so similar to existing products or services that users may be misled. Now, policies around metadata. Avoid profane or vulgar language. Avoid word blocks or long list of words. Don't include unattributed or anonymous user testimonials. Now look at best practices for app title and developer name. There are several violations in the app title and developer name here. Avoid words like top or number one that indicates or imply ranking. Don't use caps, unless your brand is capitalized. Don't use special character sequences that are irrelevant to the app. Don't use emoticons or emojis in the title or developer name. Words like free or no ads promote deals. Don't use such words. Now best practices for app descriptions. You have short description, which allows up to 80 characters and full description with 4,000 characters limit. Give users summary of your biggest benefits in short description because some users make decisions quickly and use only short descriptions to decide on whether or not to download your app. Keep your full description concise. Users may only read the first few sentences. Don't repeat your short description in your full description. This example of full description violates several rules. Avoid words such as free, perfect, best, number one, as these are indicative of Google Play store performance. Avoid unnecessary repeating keywords or phrases in an attempt to improve search results. Avoid phrases that tell user to install or download. This is good example of full description. It covers what your app does, who will be most interested in your app, special or unique features of your app, unique benefits of using your app, rewards they can earn and how. You will see best practices for graphics in the next episode. So stay tuned.