Android Device Streaming, powered by Firebase, is now in Beta
Validating your app on a range of Android screens is an important step to developing a high quality Android app. However, getting access to the device you need, when you need it, can be challenging and time consuming. From trying to reproduce a device specific behavior on a Samsung device to testing your adaptive app layouts on the Google Pixel Fold, having the right device at the right time is critical.
To address this app developer use case, we created Android Device Streaming, powered by Firebase. With just a few clicks, you and your team can access real physical devices, such as the latest Pixel and Samsung devices, and use them in the IDE in many of the ways you would use a physical device sitting on your desk.

Today, Android Device Streaming is in beta and is available to all Android developers using Android Studio Jellyfish or later. We’ve also added new devices to the catalog and introduced flexible pricing that provides low-cost access to the latest Android devices.
Read below to learn what changes are in this release, as well as common questions around uses, security, and pricing. However, if you want to get started right away and try Android Device Streaming at no cost, see our getting started guide.
What can you do with Android Device Streaming?
If you’ve ever used Device Mirroring, you know that Android Studio lets you see the screen of your local physical device within the IDE window. Without having to physically reach out to your device, you’re able to change the device orientation, change the posture of foldables, simulate pressing physical buttons, interact with your app, and more. Android Device Streaming leverages these same capabilities, allowing you to connect and interact with remote physical devices provided by Firebase.

When you use Android Studio to request a device from Android Device Streaming, the IDE establishes a secure ADB over SSL connection to the device. The connection also lets you use familiar tools in Android Studio that communicate with the device, such as the Debugger, Profiler, Device Explorer, Logcat, Compose Live Edit, and more. These tools let you more accurately validate, test, and debug the behavior of your app on real OEM hardware.
What devices would my team have access to?
Android Device Streaming gives you and your team access to a number of devices running Android versions 8.1 through 14. You have access to the latest flagship devices from top device manufacturers, such as Google Pixel and Samsung. You can expand testing your app across more form factors with access to the latest foldables and tablets, such as the Samsung Tab S8 Ultra.

And we’re frequently adding new devices to our existing catalog of 20+ device models, such as the following recent additions:
- Samsung Galaxy Z Fold5
- Samsung Galaxy S23 Ultra
- Google Pixel 8a
Without having to purchase expensive devices, each team member can access Firebase’s catalog of devices in just a few clicks, for as long as they need—giving your team confidence that your app looks great across a variety of popular devices.

As we mentioned at Google I/O ‘24, we’re partnering with top Original Equipment Manufacturers (OEMs), such as Samsung, Google Pixel, Oppo, and Xiaomi, to expand device selection and availability even further in the months to come. This helps the catalog of devices grow and stay ahead of ecosystem trends, so that you can validate that your apps work great on the latest devices before they reach the majority of your users.
Is Android Device Streaming secure?
Android Device Streaming, powered by Firebase, takes the security and privacy of your device sessions very seriously. Firebase devices are hosted in secure global data centers and Android Studio uses an SSL connection to connect to the device.
A device that you’ve used to install and test your app on is never shared with another user or Google service before being completely erased and factory reset. When you’re done using a device, you can do this yourself by clicking “Return and Erase Device” to fully erase and factory reset it. The same applies if the session expires and the device is returned automatically.

How much does Android Device Streaming cost?
Depending on your Firebase project’s pricing plan, Android Device Streaming users can use Android Device Streaming with the following pricing:
- On June 1, 2024, for a promotional period:
- (no cost) Spark plan: 120 no cost minutes per project, per month
- Blaze plan: 120 no cost minutes per project, per month, 15 cents for each additional minute
- On or around February, 2025, the promotional period will end and billing will be based on the following quota limits:
- (no cost) Spark plan: 30 no cost minutes per project, per month
- Blaze plan: 30 no cost minutes per project, per month, 15 cents for each additional minute
With no monthly or yearly contracts, Android Device Streaming’s per-minute billing provides unparalleled flexibility for you and your team. And importantly, you don’t pay for any period of time required to set up the device before you connect, or erase the device after you end your session. This allows you and your team to save time and costs compared to purchasing and managing your own device lab.
To learn more, see Usage levels, quotas, and pricing.
What’s next
We’re really excited for you and your team to try Android Device Streaming, powered by Firebase. We think it’s an easy and cost-effective way for you to access the devices you need, when you need them, and right from your IDE, so that you can ensure the best quality and functionality of your app for your users.
The best part is, you can try out this new service in just a few clicks and at no cost. And our economical per-minute pricing provides increased flexibility for your team to go beyond the monthly quota, so that you only pay for the time you’re actively connected to a device—no subscriptions or long-term commitments required.
You can expect that the service will be adding more devices from top OEM partners to the catalog, to ensure that device selection remains up-to-date and becomes increasingly diverse. Try Android Device Streaming today and share your experience with the Android developer committee on LinkedIn, Medium, YouTube, or X.
Source: Android Developers Blog
Deprecation of publisherReviewStatuses field in the Display & Video 360 API
Today we’re deprecating the publisherReviewStatuses
field in the Display & Video 360 API Creative
resource. The field will sunset on June 26, 2024. After the sunset, publisherReviewStatuses
will always contain an empty array in retrieved Creative
resources.
We’ve added the upcoming sunset to our list of feature deprecations. To avoid any issues, we recommend that you stop reading the publisherReviewStatuses
field from retrieved Creative
resources.
If you have questions regarding these changes, please follow the instructions on our support guide or contact us using our contact form.
Source: Google Ads Developer Blog
Long Term Support Channel Update for ChromeOS
LTS-120 is being updated in the LTS (Long Term Support) channel, version 120.0.6099.313 (Platform Version: 15662.110.0), for most ChromeOS devices.
Source: Google Chrome Releases
8 ways to “Find Pride” with Google this year

Source: The Official Google Blog
Mobile-indexing-vLast-final-final.doc
The last step of our migration to a mobile-first index will soon be complete: the small set of sites we've still been crawling with desktop Googlebot will be crawled with mobile Googlebot after July 5, 2024. Most websites do not need to do anything!
Source: Google Search Central Blog
Google Workspace Updates Weekly Recap – May 31, 2024
1 New update
Unless otherwise indicated, the features below are available to all Google Workspace customers, and are fully launched or in the process of rolling out. Rollouts should take no more than 15 business days to complete if launching to both Rapid and Scheduled Release at the same time. If not, each stage of rollout should take no more than 15 business days to complete.
Previous announcements
Completed rollouts
The features below completed their rollouts to Rapid Release domains, Scheduled Release domains, or both. Please refer to the original blog posts for additional details.
- Protect sensitive admin actions with multi-party approvals
- Configure managed iOS apps for your users’ using Google Mobile Device Management
- Gemini for Google Workspace feature Help me write now available in Spanish and Portuguese
- View recent shares in the Google Drive Activity page
- Manage spaces at scale with new Chat API functionality
- Introducing Gemini offerings for Google Workspace for Education customers
- Introducing audit logs for these API-based actions
For a recap of announcements in the past six months, check out What’s new in Google Workspace (recent releases).
Source: Google Workspace Updates
Chrome Dev for Desktop Update
The Dev channel has been updated to 127.0.6510.4 for Windows, Mac and Linux.
A partial list of changes is available in the Git log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
Daniel Yip
Google Chrome
Source: Google Chrome Releases
Chrome Beta for iOS Update
Hi everyone! We've just released Chrome Beta 126 (126.0.6478.27) for iOS; it'll become available on App Store in the next few days.
You can see a partial list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.
Krishna Govind
Google Chrome
Source: Google Chrome Releases
Chrome Dev for Android Update
Hi everyone! We've just released Chrome Dev 127 (127.0.6510.5) for Android. It's now available on Google Play.
You can see a partial list of the changes in the Git log. For details on new features, check out the Chromium blog, and for details on web platform updates, check here.
If you find a new issue, please let us know by filing a bug.
Erhu Akpobaro
Google Chrome