Feb 11, 2022 By Geoff Parent 7 min
Geoff is a writer and guest contributor to sidebar Magazine.
TL;DR: Publishing an app to the Google Play Store can seem like a daunting task. Median.co's guide to Google Play Store publishing demystifies the process, going deep into the key steps you need to take to successfully prepare and publish your app, from laying the groundwork to mastering the review process.
To publish an app to the Google Play Store, you'll need to first set up Google Play store Developer Account, then prepare your app for submission (including app signing and beta testing), optimize it with App Store Optimization (ASO) in mind, and finally, educate yourself on generally mastering the app approval process.
After you take the important step to convert a website into an app, you can now publish your hybrid/web+mobile Android app and see it potentially rank in the Google Play Store, alongside the biggest and brightest competitors in your business. Below, you'll find a step-by-step guide to help you navigate the key steps that will help you make that possible!
Publishing to the Google Play Store is the best way for users to find, download, and update your Android app safely and easily.
Given Google’s commitment to delivering a consistent, high-quality user experience, it’s not surprising that there are a number of requirements for apps to be approved within the Play Store. Here’s a quick overview of what we cover in this guide to publishing your app to the Google Play Store:
Want the full scoop on how to publish an app to the Google Play Store? Keep reading!
Publishing to the Google Play Store, as well the Apple App Store, only serves to increase the discoverability of your app. By creating an android app, you're unlocking a vast and new audience to connect with.
But, since the app marketplace is crowded with competitors, it is important to take all the required steps to ensure the successful publishing of your app, as well as its ongoing growth and success.
Remember: Prior to getting started, it’s important to review Google’s full list of content policies for apps listed in their store and make any necessary changes to ensure your app is 100% compliant.
Google will restrict specific types of content within apps. If your app is subject to external regulation (e.g., financial services), you'll need to comply with applicable local regulations and provide documentation.
If your app includes user generated content, you'll need to demonstrate that you have adequate moderation policies and procedures in place to remove objectionable content.
Google will not approve apps for the Play Store that encourage or induce infringement of intellectual property rights. You should not rely on misleading, unauthorized, or unfair use of other people’s work. If you are using intellectual property from another party, you may be asked to provide a licensing agreement to verify permissions.
Google strictly prohibits apps that are deceptive, malicious, or intended to abuse or misuse any network, device, or personal data. Additionally, apps that contain Malware are strictly prohibited from Google Play, given how harmful it can be to users.
While Google does support a number of app monetization strategies, it’s important to review their monetization guidelines to ensure your app is compliant and published without issue.
Apps that spam users are strictly prohibited in the Google Play Store. These can include apps that send unsolicited messages, apps that are highly repetitive, and apps that are low-quality. The commitment to barring these types of apps is part of Google’s broader initiative to ensure a “minimum functionality” of all the apps available in the Play Store.
Google puts a premium on app performance, design and end user utility. By adhering to these core standards, developers can ensure that their apps are elevated beyond a mobile site or repackaged website. Ultimately, Google reinforces the need for developers to create apps that are stable, engaging, responsive and that deliver an excellent user experience. Google will reject apps that:
When it comes to building a high-quality app or game, Google’s guidelines outline the most important components to keep in mind throughout the development process, including content, user experience and technical performance.
Whether you're publishing a webview app, native app, or hybrid app to the Google Play Store, keeping Google's guidelines top of mind will ensure your success -- the first time.
At a high level, these guidelines recommend that you:
Adding a native sidebar menu and/or a bottom tab bar menu is an excellent way to create easy, intuitive navigation through your app. This article on best practices for app navigation and app UI will give you insight into *exactly* what you should include on this front.
Create an intuitive interface that supports Android visual design and interaction patterns, and optimize for performance, stability and compatibility to meet your user’s expectations.
Apps shouldn’t contain footer text and menus!
If you want to show your logo on every page, contain it to an area as opposed to letting it consume the entire screen.
Ensure that forms are scaled large enough so that users can easily complete them on their mobile devices.
Connecting users and driving deeper engagement will provide a richer experience and make users more likely to stay connected long-term. Release regular app updates and content refreshes to drive engagement and stay top-of-mind.
Ensure your app has a robust privacy policy, and that you are protecting your users’ personal information. Be transparent in your communication and responsiveness with users and address concerns promptly. This will show your users that you value their feedback and appreciate their support and loyalty.
In addition to following the Play Store guidelines, you’ll also want to think about how you plan to monetize your app. Will you offer it for free and rely on in-app purchases or ads, or will you charge a download fee? Consider your target audience and what you think they would be willing to pay for.
It’s crucial to rigorously test your app to ensure that it both meets Google’s minimum functionality requirements and delivers a seamless, intuitive user experience. While you are of course looking for crashes and bugs, you are also testing to ensure your app functions “like an app”. Put yourself in the shoes of the end user:
After you have set up your developer account and can access Google Play Console using the instructions below, you’ll have the ability to share app bundles and APKs with a small group of up to 100 testers for initial testing and quality assurance. Once you have set up your App content and store listing, you’ll also have the ability to run the following tests:
At this point, it’s time to ensure you have all the necessary profiles and accounts set up and prepare for submission.
The first step to getting your native app or webview app (or find a good hybrid app example here) in the Google Play Store is creating your Google Play Developer Account, which allows access to the Google Developer Console – the platform you’ll use to manage your app submission and testing, monitor performance, and interact with users.
Setting up an account is straightforward, and involves creating a traditional Google account (if you don’t already have one), paying a registration fee, and agreeing to the Google Play Developer Distribution Agreement.
Your Developer Account must be created and compliant before you can submit your app for review and publish on the Google Play Store. If you’re creating an app for an organization or a business, you must be able to submit:
If you are looking to set up your Google Developer Account, click here to get started.
With your developer account set up, you’ll have access to your Google Play Console dashboard — a central hub where you can upload, test, submit and manage your Android apps.
The first step in uploading your app to Google Play Console is creating a new app. To create a new app, navigate to All apps>Create app and fill in the basic information about your application.
You will have the opportunity to change or edit these attributes later when you are reviewing/creating your store listing.
You will now need to create your Android Package Name. Your app’s Android Package Name is a unique text identifier for your app that is registered with Google. It is only visible to users in your app's Google Play Store URL and cannot be changed once your app is published.
Google recommends you follow the reverse domain name notion, e.g. com.yourdomain.app. Note that dashes or spaces are not allowed. You cannot start any section of the package name with a number.
With the basic information about your app filled in, you can now upload your app file to Google Play Console. Here is some key information you should know during this process.
An Android App Bundle (AAB) is a publishing file format that includes all your app’s compiled code and resources, and defers APK generation and app signing to Google Play. As of August 21, 2021, all new Android apps submitted to the Google Play Store must be AAB files.
TIP: If you build your Android app with Median, we will generate the necessary AAB file needed for you to successfully upload your app to the Google Play Console.
Code signing an app is a way of verifying its authenticity. All Android apps are signed with a private key to ensure that your app’s code has not been altered since it was signed. Google has its own app signing infrastructure known as Play App Signing.
To upload an Android App Bundle to your Google Play Console, you must enroll in and use Play App Signing.
With Play App Signing, Google generates an app signing key for your app when you upload it to the Google Play Console.
Google will also manage and protect your app's signing key for you and use it to sign optimized, distribution APKs that are generated from your app bundles.
For extra security, Google recommends generating a separate upload key and signing your app with that upload key before uploading it to the Google Play Console and proceeding with submission.
If you decide not to create and sign your app with an upload key, you will continue to use your app signing key as your upload key to sign each subsequent release/update of your app. While this is acceptable, it’s highly advisable to keep your upload key and app signing key distinct from one another.
Once you have downloaded the Android App Bundle file from your app management page, it’s time to upload the file to your Google Play Console. From the Play Console homepage, follow these instructions:
With your AAB file successfully uploaded, it’s now time to navigate back to the Play Console homepage to fill out necessary information about your app. You will need to provide detailed metadata and content information about your app before submitting it for review. This is done in two parts:
Creating a compelling Google Play Store listing is essential to attract and engage potential users.
Start by crafting a concise and relevant title that reflects the core functionality of your app. Write a clear and engaging description, highlighting the key features and benefits that make your app unique. Use high-quality app screenshots and graphics to visually showcase your app’s design and functionality.
Ensure your app’s metadata, including categories and keywords, are optimized for App Store Optimization (ASO) to improve your app’s visibility in search results. Set the right pricing strategy, considering whether your app will be free, paid or offer in-app purchases.
As you complete the information fields, keep the following guidelines in mind:
You can find these fields in the App Content section of your Google Play Console dashboard. You do not need to fill out this information in any particular order, however, it must be completed fully in order to proceed to app review.
You will need to provide detailed metadata and content information about your app before submitting it for review. This is done on your Google Play Console dashboard under Store Presence > Store Settings.
Simply follow the information fields and fill out the metadata as accurately as possible. It’s important to include quality descriptions, screenshots, previews, categorizations, etc., that accurately reflect the core experience of the app.
TIP: Now is also a good time to revisit the initial metadata you created for your app (App Name, Default Language, App or Game, Free or Paid) to ensure it is still accurate.
Now that you have set up your app and completed the content and metadata information, you can submit your app for review.
Note: If you are releasing an update you can choose to rollout to all users immediately or to stage the rollout to users over time. Click here to learn more about releasing an app update.
TIP: If you build your Android app with Median, we will generate the necessary AAB file needed for you to successfully upload your app to the Google Play Console.
Preparing your app for review is a critical step to ensure it meets platform guidelines and offers a seamless user experience.
Start by thoroughly testing your app on various devices and Android versions to identify and fix any bugs or issues. Ensure that your app complies with Google Play Store guidelines, including content policies and app functionality requirements and provide all the required information, like your app’s Privacy Policy, declaration on ads, and details about your app’s access.
Optimize your app’s performance and minimize its size for faster downloads and ensure your app’s metadata is complete, including title, description, screenshots, and keywords.
Beta testing – or Closed Testing – your app is highly recommended at this point because it allows your app to gather feedback and identify potential improvements before you formally submit it for review.
After uploading your app to the Google Play Console, you can monitor its status across various stages, known as tracks, including draft, testing and production. The review process dictates your app’s track.
For instance, your app remains in the “testing” track until it is approved by the Google Play Console. This is also knows as the Open Testing phase, which allows you to test with a large group of users via your app’s test version on Google Play. To publish a draft of your app, you’ll need to initiate a release rollout.
Once your app is approved, you can transition to the production track, making it publicly available.
Following this, you’ll want to regularly update your app to maintain its relevance, performance, and user satisfaction. Monitoring user feedback and app performance metrics helps to identify areas for improvement and inform future updates.
Once that your app is available to users, you want to ensure they can easily find it by optimizing titles, descriptions, promo text, supporting graphics, and accessibility. Optimizing your app listing with App Store Optimization (ASO) in mind for the Play Store will drive downloads and attracting users. Here are a few tactics to help up your ASO:
Title: Keep your app title to a maximum of 30 characters. Incorporate keywords that are highly relevant to your app.
Description: This is the text that appears under your screenshots on your app page and should not exceed 80 characters. Keep conversion in mind when writing your short description.
Promo Text: This is space for a longer description – and your chance to convince users to download your app. Repeat high priority keywords but avoid keyword stuffing as Google penalizes this practice. Aim for a keyword density between 1% to 2%.
Screenshots, graphics and Image Assets: Present your app’s most importance features with high-quality preview images and a unique selling proposition. Your App Icon will be visible everywhere, so use it to convert users. Consider your brand identity and how your design choices reinforce your app’s purpose.
Equitable Access: Ensure your app is accessible to all users, regardless of their abilities or disabilities. Give easy-to-understand details and make sure your app can be used by people from different places, not just by translating words, but by making it work well for them, too.
It's also a good idea to think of the broader marketing outreach for your app (and doing this well in advance). Why? A go-to-market app strategy is key to ensuring you're effectively and continually reaching new audiences on the right channel.
The review and approval process typically takes 1-3 days to complete (although some reviews may take longer), during which time your app is thoroughly reviewed against the Play Store guidelines. It’s important to monitor the status of your app’s review from the Google Developer Console during this time.
You can learn more about the different statuses your app may encounter during the review process: Click here for the different situations.
It depends but the process takes much longer if you have a non-business developer account.
If you have a personal Play Console developer account, Google Play now requires that you test your app with a minimum of 20 people, and for a period of at least two weeks, before you can apply for the release of your app in the public listings of the Play Store. Learn more about the Play Stores more rigorous testing rules here.
Congratulations! You have successfully submitted your app for review.
If you’re looking for more support as you try to get your Android App published on the Google Play Store, try Median.
Our highly intuitive online app builder makes it easy to convert your existing website or web-based application into an immersive, visually stunning native Android and iOS app.
Median also provides end-to-end app publishing services. Since 2014, we’ve helped our customers by publishing over 3,500 apps with a 97% approval rate to the Google Play Store and Apple App Store.
Our team manages the publishing process from start to finish, ensuring compliance with app store guidelines, and seeing that your app is approved and available for download as quickly as possible.
Frequently asked questions
Google Play requires that all new apps and updates target at least API level 34 (Android 14) to ensure compatibility with the latest Android features and security updates. This requirement helps maintain a high standard of app quality and user experience. Developers should regularly check the Google Play Console for updates on API level requirements and ensure their apps are compliant to avoid potential issues with app updates or new releases.
To ensure your app complies with Google Play Store policies, thoroughly review the Google Play Developer Policy Center guidelines. Regularly check for updates, adhere to content and privacy policies, avoid prohibited content, and ensure your app meets all technical requirements. Testing your app for compliance before submission can help avoid rejections.
Common reasons for app rejection on Google Play include violations of content policies (such as inappropriate content or copyright infringement), privacy policy issues, technical issues (such as crashes or bugs), misleading metadata, and non-compliance with advertising guidelines. Ensuring your app adheres to all policies and guidelines can help prevent rejections.
The approval process for an app on Google Play can vary. Typically, it takes a few hours to a few days. However, it can take longer if the app requires a more detailed review or if there are issues that need to be addressed. Keeping your app compliant with Google Play's guidelines can help expedite the approval process.
After your app is published on Google Play, monitor its performance using the Google Play Console. Collect user feedback, track ratings and reviews, and address any issues promptly. Regularly update your app to fix bugs, add new features, and improve user experience. Additionally, optimize your app's metadata and visuals to enhance visibility and attract more downloads.