Program Overview

Welcome to Android Q Beta, a program that gives you everything you need to make your apps compatible and build for the next version of Android. It's free, and you can get started right away just by downloading the Beta SDK and tools.

Hardware and emulator system images

Run and test your apps on Pixel devices and the Android Emulator.

Latest platform code

We’ll provide multiple updates during the Beta, so you’ll be testing against the latest platform changes.

New behaviors and capabilities

Start work early to support new platform behaviors.

Feedback and support

Report issues and give us feedback using our issue tracker. Connect with other developers in the Developer Community.

Timeline and updates

The Android Q Beta program runs from 13 March 2019 until the final public release to AOSP and OEMs, planned for Q3 2019.

At key development milestones, we’ll deliver updates for your development and testing environment. Each includes SDK tools, Beta system images, emulators, API reference, and API diffs. The milestones are listed below.

  • Beta 1 (initial release, beta)
  • Beta 2 (incremental update, beta)
  • Beta 3 (incremental update, beta)
  • Beta 4 (final APIs and official SDK, Play publishing, beta)
  • Beta 5 (release candidate for testing)
  • Beta 6 (release candidate for final testing)
  • Final release to AOSP and ecosystem

For developers, the focus during the early part of the Beta program is on making sure your current app is compatible with the new platform, and providing early feedback. In the later part of the Beta—but ongoing throughout and beyond it—focus on adopting new features in your app and targeting the new platform.

Please see the migration guide for easy steps to make your app compatible with the new platform, then target the new platform when you're ready.

The first three Beta milestones provide an early test and development environment that help you identify compatibility issues in your current apps and plan migration or feature work needed to target the new platform. This is the priority period in which to give us your feedback on features and APIs and file compatibility issues — for all of these, please use the issue tracker. You can expect some API changes across these updates.

At Beta 4 you’ll have access to the final APIs and SDK to develop with, as well as updated beta system images to test system behaviors and features. Android Q will provide a standard API level at this time. You can begin final compatibility testing of your legacy apps and refine any new code that is using the APIs or features.

Also starting in Beta 4, you’ll be able to publish apps to devices running Android Q at the official API level, such as consumer devices that have opted into the Android Beta program. You can publish into the Google Play alpha and beta channels first, so you can test your apps with Android Beta consumers before distributing broadly on the store.

At Beta 5 and 6 you’ll have release candidate builds—which include the final APIs and near-final system images—for development and testing.

As you test and develop, we strongly recommend keeping your development environment up-to-date as Beta updates are released.

We’ll notify you when Beta updates are available via the Android Developers Blog, as well as this site and the Android Developer Community.

What's included in the Android Q Beta program?

The Android Q Beta program includes everything you need to test your existing apps on a variety of screen sizes, network technologies, CPU/GPU chipsets, and hardware architectures.

SDK tools

With Android Studio, you can download these components through the SDK Manager:

  • Q Beta SDK and tools
  • Q Beta emulator system image (32-bit & 64-bit)
  • Q Beta emulator system image for Android TV (32-bit)

We’ll provide updates to these development tools at each milestone as needed.

For complete SDK setup instructions, see the migration guide.

System images for a variety of hardware devices

The Android Beta program includes system images for a variety of Pixel devices that you can use for developing and testing. See Get Android Q for details.

OTA Updates for Pixel through the Android Beta for Pixel program

If you have a Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Pixel 3, or Pixel 3 XL device, you can enroll the device in the Android Beta program to get updates to Android Q Beta over-the-air (OTA). For details, see the Get Android Q page or visit to enroll.

Documentation and sample code

These documentation resources are available on the Android Q Beta site to help you learn about Android Q:

API Reference and diff report

The full Beta API reference is available online. New APIs are watermarked for visibility and show "Android Q" as the API level. Note that you can only use these APIs if you are building with the Android Q Beta SDK.

Note: To show the Q APIs, make sure to set the API Level selector to "Q" in the left navigation on any reference page.

To get a detailed view of new, modified, and removed APIs in each Beta release, we recommend starting with the diff reports:

Changes in the diff reports link you to the related API reference documentation.

Support resources

As you test and develop on the Beta, please use these channels to report issues and give feedback:

  • Android Beta Developer issue tracker is your primary feedback channel. You can report bugs, performance issues, and general feedback through the issue tracker. You can also check for known issues and find workaround steps. We’ll keep you updated on your issue as it’s triaged and sent to the Android engineering team for review.
  • For details on how to report various kinds of issues, see the Feedback page.
  • The Android Beta Developer Community is a community where you can connect with other users and developers working with Android Beta. You can share observations or ideas or find answers to questions.

Targeting, Beta APIs, and publishing

The Android Q Beta provides a development-only system and Android library that does not have a standard API level. If you want to target the new platform and build with the new Android Q APIs, you target the Beta version of Android Q by setting your app's targetSdkVersion to 29, and both your minSdkVersion and Gradle compileSdkVersion to 29. For details, see how to update your build configuration for Android Q.

The Android Q Beta delivers Beta APIs — the APIs will not be official until the final SDK is released. This means that you can expect API changes over time, especially during the initial weeks of the program. We’ll provide a summary of changes to you with each update of the Android Q Beta.

Note: Although Beta APIs may change, underlying system behaviors are typically stable and ready for testing against right away.

Google Play prevents publishing of apps targeting the Android Q Beta. When the final SDK is available, you’ll be able to target the official Android Q API level and publish your app to Google Play via the alpha, beta, and production release channels. Meanwhile, if you want to distribute an app targeting Android Q to testers, you can do so via email or by direct download from your site at any time.

How to get started

To get started, install Android Q on your hardware device or set up an emulator for compatibility testing. See Get Android Q for details. Then review the migration guide for an outline of steps for both compatibility testing and building for Android Q.

Thank you for participating in the Android Q Beta program!