publish

Prepare a ChromeOS app for launch on Google Play

ChromeOS supports Android Apps⁠ and Progressive Web Apps⁠, both of which can be discovered by users on Android and Chromebooks via Google Play. When you publish to Google Play, your app becomes available to billions—but it still has to be optimized for better reach.

When an app is properly optimized for ChromeOS, it can take advantage of the features that make Chromebook apps shine, such as large screens and keyboard support. Follow the ChromeOS optimization guidelines⁠ to identify changes that may need to be made to your app to provide the best user experience.

Specifically:

  • X86 architecture⁠: Many ChromeOS devices use an x86 architecture, whereas most Android phones have ARM chipsets. Apps with Android NDK code have additional publishing considerations.
  • Large screens⁠: ChromeOS devices have generally larger screens than most Android devices—and can support external monitors. Follow our design recommendations⁠ for a better user experience on larger screens.
  • Resizable windows⁠: On ChromeOS, users may resize and reposition their windows on-the-fly, and apps may transition from portrait to landscape based on position.
  • Multiple input devices⁠: ChromeOS devices may use a touch interface, keyboard and mouse, or controller—and may switch between input methods⁠.

For the best user experience, don’t just support the unique features of ChromeOS—use them to your advantage. Once you’ve optimized your app for ChromeOS devices, you can move on to testing and publishing.

Test your app or game before launch

As with Android apps, ChromeOS apps may be run on a wide variety of platforms. Thorough testing is critical to launching the best possible app or game. Visit the resources below to learn more about testing for Google Play:

  • Linting⁠: automatically check your app’s code for potential issues for ChromeOS.
  • Internal testing⁠⁠: test entirely new apps or features, focusing on early stability and performance.
  • Closed testing⁠⁠: test the app with a private community without impacting ratings or reviews.
  • Open testing⁠⁠: test publicly and/or with a larger group of users without impacting ratings or reviews.

Run beta tests across various devices to get critical feedback before launch, then “soft launch” to select audiences to confirm KPIs and build up public ratings.

Finally, launch worldwide with confidence—and fewer surprises.

Prepare your app for launch

Before you publish your game, coordinate your plans and build interest. Use the following Google Play checklists to prepare for the launch:

Sample launch schedule

Keep your publishing on track with the below schedule. When creating your schedule, allow enough time for your app to go through review.

WeekTask

1

Review the best practices for publishing and releasing your app or game on Google Play⁠.

3

Review the Play Console Policy Center⁠ to make sure your app is compliant.

7

Finalize the build of your app for ChromeOS and supported architectures.

8

Begin testing your app in phases, including internal, closed, and open testing.

10

Submit your app for review via managed publishing⁠⁠. A typical review will take approximately 7 business days. Please do not resubmit your app during the review cycle as it will reset the cycle.

11

Check your submission to make sure it has been approved.

12

Once your app is approved, you will be able to publish it on your launch date⁠⁠.

Additional resources

Increase your chances of a successful launch by reading more about Google Play’s policies and standards—and by learning more about the process of developing and optimizing for ChromeOS.

Policy and compliance

Meet Google Play’s policies and standards by following Google’s Developer Program Policies⁠⁠. The earlier you work to meet these specifications, the smoother your development and publishing process will be.

  • Policy Coverage⁠⁠: Details on Google Play’s policy coverage and enforcement process. This includes how Google Play Protect, malware protection, and privacy alerts work to prevent malicious activity by apps.
  • Privacy Policy⁠⁠: All apps must post a privacy policy link within Play Console and the app itself. The privacy policy must disclose how the app accesses, collects, uses, and shares user data.
  • User Data⁠⁠: Google Play requires that developers be transparent in how their app handles user data, including access, collection, use, handling, and sharing the data from the app.
  • Target API Level⁠⁠: If you want your app to run on Android devices, you must meet a target API level. All apps must meet a target API level of 30 or above (existing apps) or 31 or above (new apps).
  • App Promotion⁠⁠: Apps that directly or indirectly engage in, or benefit from promotion practices that are deceptive or harmful to users or the developer ecosystem violate the Developer Program Policies. Follow these guidelines⁠⁠ to ensure the content is of high quality and delivers the best experience for the users.
  • Apps for Children and Families⁠⁠: Apps designed specifically for children must participate in the Designed for Families program and must follow the Google Play Families Policy requirements. Only select more than one age group for your app’s target audience if your app is designed for and is appropriate for users within the selected age group(s).
  • Payments Policy⁠⁠: Google Play’s billing system is required for developers offering in-app purchases of digital goods and services distributed on Google Play, and it must be used through Billing Library version 4 or newer⁠⁠. Learn more about Google Play’s Payments Policy on the Policy Help Center page⁠⁠.
  • Play Console Policy Center⁠⁠: The Play Console Policy Center contains all policies currently in effect—and the policy archive. Consult Policy Deadlines⁠⁠ and Policy Status⁠⁠ for more specific information.

Tutorials and learning

Learn more about publishing on Google Play and developing for ChromeOS with these tutorials and resources.