Google Workspace Updates Weekly Recap – July 11, 2025

New updates

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.

Veo 3 is now available in the Gemini app for select Workspace users 
At Google I/O 2025 we introduced Veo 3, our new latest video generation model that can generate video with audio. Today, Veo 3 is now available in the Gemini app for select Workspace customers. 

With Veo 3 you'll notice real-world physics and accurate lip syncing - this includes things like traffic noises in the background of a city street scene, birds singing in a park, and even dialogue between characters. We also introduced a new photo to video feature that allows you to upload a photo and create an 8-second video. You can get creative by animating everyday objects, bringing your drawings and paintings to life or adding movement to nature scenes. 

There is a limit of 3 daily uses for enterprise and education users and 5 daily uses for those with the Google AI Ultra for Business add-on. When you are approaching this limit, you’ll see a warning message in the UI. Teams can also generate video clips with Veo in Google Vids as well. | Rolling out now to Rapid Release and Scheduled Release domains. | Available when using the Gemini app with Google Workspace Business Standard and Plus, Enterprise Standard and Plus and the Gemini Business and Education add-ons. | Visit our Help Center to learn more about generating videos with Gemini and which countries & territories. At the moment, Veo 3 is only available on the web and the Gemini mobile app and for users 18+.

Adding Google Calendar sharing to Android devices
In Google Calendar, you can share any calendar you own or have permission to share with other users and groups. This functionality is currently available on web only, and this week we’re excited to extend it to Android devices. The same settings available on web will now be available on your mobile device, which includes the ability to share a calendar with individuals, a domain or the entire public. | Rolling out now to Rapid Release and Scheduled Release domains. | Available to all Google Workspace customers, Workspace Individual Subscribers, and users with personal Google accounts. | Visit the Help Center to learn more about sharing your calendar with someone
Adding Google Calendar sharing to Android devices
Automatically level audio across a video in Google Vids with balance sound 
In May, we preannounced the ability to easily adjust sound levels across videos in Google Vids. Starting today, users can automatically level the volume of audio and video clips in their Vids and add audio ducking to background music, which automatically lowers (or "ducks") music when another audio or video clip’s volume starts playing. | Rollout to Rapid Release domains is complete; launch to Scheduled Release domains planned for July 21, 2025. | Available to Google Workspace customers with access to Google Vids. | Visit the Help Center to learn more about controlling audio timing, balance & transitions with audio tracks.

balance sound in Vids
Gemini summary cards now available in Gmail on web 
In May, we introduced Gemini summary cards in Gmail on Android and iOS devices. This week, we’re excited to announce that summaries will be available on web as well, at the top of emails for messages where a summary is helpful, such as longer email threads or messages with several replies. | Rollout to Rapid Release and Scheduled Release domains is complete. | Available to Google Workspace Business Starter, Standard and Plus; Enterprise Starter, Standard and Plus; customers with the Gemini Education or Gemini Education Premium add-on, and anyone who previously purchased a Gemini Business or Gemini Enterprise add-on. | Visit the Help Center to learn more about collaborating with Gemini in Gmail. 

Introducing a refreshed user interface in Google Drive for Desktop 
In order to provide desktop users with a centralized area to easily manage all of their Drive files in one place, we’ve introduced improvements to Google Drive for desktop. Specifically, users will now see important information, such as sync activity, notifications, shared files and more in a single view. | Rolling out now to Rapid Release and Scheduled Release domains. | Available to all Google Workspace customers, Workspace Individual Subscribers, and users with personal Google accounts. | Visit the Help Center to learn more about Google Drive for desktop. 
Introducing a refreshed user interface in Google Drive for Desktop
A new look and feel is coming for the Workspace Updates Blog 
We’re excited to share that a refreshed experience for the Workspace Updates Blog will be launching on Monday, July 14. Some of the improvements you’ll notice are: 
  • A completely refreshed user interface that brings the Workspace Updates Blog inline with other official Google channels. 
  • A compact layout that allows you to quickly scan multiple posts, making it easier to find the announcements that matter most to you. 
  • Easier navigation with product tags neatly categorized at the top of the page, and quick links to other resources like the Release Calendar. 
  • Auto translation for 100+ languages using Google translate right from the footer of the website. 
These updates will also be available when viewing the Workspace Updates Blog on mobile.

Previous announcements

The announcements below were published on the Workspace Updates blog earlier this week. Please refer to the original blog posts for complete details.

Use Gemini in Google Drive to execute basic organizational tasks 
Starting this week, we’ve enhanced Gemini’s organizing capabilities in Drive by allowing you to use natural language to move selected files into the folder you choose. | Learn more about using Gemini in Google Drive. 

Google Drive Events API now available in Developer Public Preview 
Google Drive is now integrated with the Workspace Events API, which allows third-party developers to create subscriptions on Drive items and receive notifications via Cloud Pub/Sub when those resources change. | Learn more about the Google Drive Events API. 

Improved email notifications following Google Meet calls, plus new sharing controls for meeting hosts
We’re improving the email notification that includes the notes doc when you use “Take notes for me” in Google Meet. The email will now include a summary of the meeting as well as “suggested next steps” in addition to the link to the notes document. Including this information gives meeting invitees a quick, helpful overview of the meeting in one place. | Learn more about email notifications for Meet calls. 

Manage email subscriptions from a single location in Gmail 
Last year, we introduced web and mobile updates that enable you to unsubscribe from individual emails in Gmail more easily. Today, we’re building upon this with Gmail's new "Manage subscriptions" feature. | Learn more managing subscriptions

Search for embedded content in Google Sites 
Starting today, we're making it easier to find information within a Google Site. Previously, searching in a site only showed results from the text directly on the pages. Now, when you perform a search, the results will also include content from within embedded files, such as Google Docs, Sheets, Slides, and PDFs. | Learn more about searching for embedded content in Sites. 

Drive IRM Update: More Control for File Owners and Shared Drive Managers 
Now, individual file owners and shared drive managers can apply printing, copying, and downloading restrictions to users with edit permissions as well. Editors and owners can still edit the document itself, however they can only copy and paste document content within the document itself. | Learn more about Drive IRM

Introducing Lucidchart and Lucidspark apps in Google Chat 
Lucidchart, an app that helps users collaborate on diagrams, such as flowcharts, wireframes, entity relationship diagrams, and more, and Lucidspark, a virtual whiteboard tool, are two third-party add-ons already available across Workspace apps, such as Docs and Meet. This week, we’re excited to announce support for both of these apps in Google Chat. | Learn more about Lucidchart and Lucidspark apps in Google Chat.

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.

Rapid Release Domains: 
Scheduled Release Domains: 
Rapid and Scheduled Release Domains: 
For a recap of announcements in the past six months, check out What’s new in Google Workspace (recent releases).

This Week in Open Source #3

This Week in Open Source for July 11, 2025

A look around the world of open source
by Daryl Ducharme, Erin McKean & amanda casari, Google Open Source Programs Office

We took a break as there was a holiday in the US that shortened our work week, but we are back to share what our open source world has to offer.

Upcoming Events

  • July 14-19: The 26th annual Debian Conference (DebConf) for Debian contributors and users interested in improving Debian is in Brest, France.
  • July 24-29: GUADEC 2025, the Gnome community's largest conference is in Brescia, Italy.
  • July 31-August 3: FOSSY (Free and Open Source Software Yearly) will be held in Portland, Oregon and is focused on the creation and impact of free and open source software, uplifting contributors of all experience.

Open Source Reads and Links

What exciting open source events and news are you hearing about? Let us know on our @GoogleOSS X account.

Dev Channel Update for ChromeOS / ChromeOS Flex

The Dev channel is being updated to OS version 16328.18.0 (Browser version 139.0.7258.33) for most ChromeOS devices. 

If you find new issues, please let us know one of the following ways

  1. File a bug

  2. Visit our ChromeOS communities

    1. General: Chromebook Help Community

    2. Beta Specific: ChromeOS Beta Help Community

  3. Report an issue or send feedback on Chrome

Interested in switching channels? Find out how.

Andy Wu,
Google ChromeOS

Dev Channel Update for ChromeOS / ChromeOS Flex

The Dev channel is being updated to OS version 16328.18.0 (Browser version 139.0.7258.33) for most ChromeOS devices. 

If you find new issues, please let us know one of the following ways

  1. File a bug

  2. Visit our ChromeOS communities

    1. General: Chromebook Help Community

    2. Beta Specific: ChromeOS Beta Help Community

  3. Report an issue or send feedback on Chrome

Interested in switching channels? Find out how.

Andy Wu,
Google ChromeOS

Transition to using 16 KB page sizes for Android apps and games using Android Studio

Posted by Mayank Jain – Product Manager and Jomo Fisher – Software Engineer

Get ready to upgrade your app's performance as Android embraces 16 KB memory page sizes

Android’s transition to 16 KB Page size

Traditionally, Android has operated with the 4 KB memory page size. However many ARM CPUs (the most common processors for Android phones) support the larger 16 KB page size, offering improved performance gains. With Android 15, the Android operating system is page-size-agnostic, allowing devices to run efficiently with either 4 KB or 16 KB page size.

Starting November 1st, 2025, all new apps and app updates that use native C/C++ code targeting Android 15+ devices submitted to Google Play must support 16 KB page sizes. This is a crucial step towards ensuring your app delivers the best possible performance on the latest Android hardware. Apps without native C/C++ code or dependencies, that just use the Kotlin and Java programming languages, are already compatible, but if you're using native code, now is the time to act.

This transition to larger 16 KB page sizes translates directly into a better user experience. Devices configured with 16 KB page size can see an overall performance boost of 5-10%. This means faster app launch times (up to 30% for some apps, 3.16% on average), improved battery usage (4.56% reduction in power draw), quicker camera starts (4.48-6.60% faster), and even speedier system boot-ups (around 0.8 seconds faster). While there is a marginal increase in memory use, a faster reclaim path is worth it.

The native code challenge – and how Android Studio equips you

If your app uses native C/C++ code from the Android NDK or relies on SDKs that do, you'll need to recompile and potentially adjust your code for 16 KB compatibility. The good news? Once your application is updated for the 16 KB page size, the same application binary can run seamlessly on both 4 KB and 16 KB devices.

This table describes who needs to transition and recompile their apps

A table describes who needs to transition or recomplie their apps based on native codebase and device size

We’ve created several Android Studio tools and guides that can help you prepare for migrating to using 16 KB page size.

Detect compatibility issues

APK Analyzer: Easily identify if your app contains native libraries by checking for .so files in the lib folder. The APK Analyzer can also visually indicate your app's 16 KB compatibility. You can then determine and update libraries as needed for 16 KB compliance.

Screenshot of the APK Analyzer in Android Studio

Alignment Checks: Android Studio also provides warnings if your prebuilt libraries or APKs are not 16 KB compliant. You should then use the APK Analyzer tool to review which libraries need to be updated or if any code changes are required. If you want to detect the 16 KB page size compatibility checks in your CI (continuous integration) pipeline, you can leverage scripts and command line tools.

Screenshot of Android 16 KB Alignment check in Android Studio

Lint in Android Studio now also highlights the native libraries which are not 16 KB aligned.

Screenshot of Lint performing a 16 KB alignment check in Android Studio

Build with 16 KB alignment

Tools Updates: Rebuild your native code with 16 KB alignment. Android Gradle Plugin (AGP) version 8.5.1 or higher automatically enables 16 KB alignment by default (during packaging) for uncompressed shared libraries. Similarly, Android NDK r28 and higher compile 16 KB-aligned by default. If you depend on other native SDK’s, they also need to be 16 KB aligned. You might need to reach out to the SDK developer to request a 16 KB compliant SDK.

Fix code for page-size agnosticism

Eliminate Hardcoded Assumptions: Identify and remove any hardcoded dependencies on PAGE_SIZE or assumptions that the page size is 4 KB (e.g., 4096). Instead, use getpagesize() or sysconf(_SC_PAGESIZE) to query the actual page size at runtime.

Test in a 16 KB environment

Android Emulator Support: Android Studio offers a 16 KB emulator target (for both arm64 and x86_64) directly in the Android Studio SDK Manager, allowing you to test your applications before uploading to Google Play.

Screenshot of the 16 KB emulator in Android Studio

On-Device Testing: For compatible devices like Pixel 8 and 8 Pro onwards (starting with Android 15 QPR1), a new developer option allows you to switch between 4 KB and 16 KB page sizes for real-device testing. You can verify the page size using adb shell getconf PAGE_SIZE.

Screenshot of the 16 KB emulator in Android Studio

Don't wait – prepare your apps today

Leverage Android Studio’s powerful tools to detect issues, build compatible binaries, fix your code, and thoroughly test your app for the new 16 KB memory page sizes. By doing so, you'll ensure an improved end user experience and contribute to a more performant Android ecosystem.

As always, your feedback is important to us – check known issues, report bugs, suggest improvements, and be part of our vibrant community on LinkedIn, Medium, YouTube, or X.

Announcing GenAI Processors: Build powerful and flexible Gemini applications

GenAI Processors is a new open-source Python library from Google DeepMind designed to simplify the development of AI applications, especially those handling multimodal input and requiring real-time responsiveness, by providing a consistent "Processor" interface for all steps from input handling to model calls and output processing, for seamless chaining and concurrent execution.

Evolving Android’s early-access programs: Introducing the Canary channel

Posted by Dan Galpin – Android Developer Relations

To better support you and provide earlier, more consistent access to in-development features, we are announcing a significant evolution in our pre-release program. Moving forward, the Android platform will have a Canary release channel, which will replace the previous developer preview program. This Canary release channel will function alongside the existing beta program.

This change is designed to provide a more streamlined and continuous opportunity for you to try out new platform capabilities and provide feedback throughout the entire year, not just in the early months of a new release cycle.

Limitations of the previous developer preview model

The Developer Preview program has been a critical part of our release cycle, but its structure had inherent limitations:

    • Developer Previews were not tied to a release channel, and had to be manually flashed to devices every time the cycle would restart.
    • Because previews were tied to the next designated Android release, they were only available during the earliest part of the cycle. Once a platform version reached the Beta stage, the preview track would end, creating a gap where features that were promising but not yet ready for Beta had no official channel for feedback.

A continuous flow of features with the Canary channel

The new Android platform Canary channel addresses these challenges directly. By flashing your supported Pixel device to the Canary release channel, you can now receive a continuous, rolling stream of the latest platform builds via over-the-air (OTA) updates.

    • You can try out and provide input on new features and planned behavior changes in their earliest stages. These changes may not always make it into a stable Android release.
    • The Canary release channel will run in parallel with the beta program. The beta program remains the way for you to try a more polished set of likely soon-to-be-released features.
    • You can use the Canary builds with your CI to see if any of our in-development features cause unexpected problems with your app, maximizing the time we have to address your concerns.

Who should use the Canary channel?

The Canary channel is intended for developers that want to explore and test with the earliest pre-release Android APIs and potential behavior changes. Builds from the Canary channel will have passed our automated tests as well as experienced a short test cycle with internal users. You should expect bugs and breaking changes. These bleeding-edge builds will not be the best choice for someone to use as their primary or only device.

The existing beta channel will remain the primary way for you to make sure that your apps are both compatible with and take advantage of upcoming platform features.

Getting started and providing feedback

You can use the Android Flash Tool to get the most recent Canary build onto your supported Pixel device. Once flashed, you should expect OTA updates for the latest Canary builds as they become available. To exit the channel, flash a Beta or Public build to your device. This will require a data partition wipe.

screenshot of the select a build menu for a Pixel 9 Pro device to get the most recent Canary build in the Android Flash Tool

Canary releases will be available on the Android Emulator through the Device Manager in Android Studio (currently, just in the Android Studio Canary channel), and Canary SDKs will be available for you to develop against through the SDK Manager.

screenshot of the Android SDK manager showing the Android Canary SDKs

Since most behavior changes require targeting a release, you can target Canary releases the way you can target any other platform SDK version, or use the Compatibility Framework with supported features to enable behavior changes in your apps.

screenshot of the Target SDK Version and the android-CANARY target

Feedback is a critical component of this new program, so please file feature feedback and bug reports on your Canary experience through the Google Issue Tracker.

By transitioning to a true Canary channel, we aim to create a more transparent, collaborative, and efficient development process, giving you the seamless access you need to prepare for the future of Android.

Start building for the next generation of Samsung Galaxy devices

Posted by J. Eason – Director, Product Management

The next generation of foldable and wearable devices from Samsung has arrived. Yesterday at Galaxy Unpacked, Samsung introduced the new Galaxy Z Fold7, Galaxy Z Flip7, and Galaxy Watch8 series. For Android developers, these devices represent an exciting new opportunity to create engaging and adaptive experiences that reach even more users on their favorite screens.

With new advancements in adaptive development and the launch of Wear OS 6, it has never been a better time to build for the expanding Android device ecosystem. Learn more about what these new devices mean for you and how you can get started.

side by side images of Samsung's Galaxy Z Flip7 on the left and Galaxy Z Fold7 on the right

Unfold your app’s adaptive potential on Samsung’s newest Galaxy devices

The launch of the Galaxy Z Fold7 and Z Flip7 on Android 16 means users are about to experience your app in more dynamic and versatile ways than before. This creates an opportunity to captivate them with experiences that adaptively respond to every fold and flip. And preparing your app for these features is easier than you think. Building adaptive apps isn’t just about rewriting your code, but about making strategic enhancements that ensure a seamless experience across screens.

Google and Samsung have collaborated to bring a more seamless and powerful desktop windowing experience to large screen devices and phones with connected displays in Android 16 across the Android ecosystem. These advancements will enhance Samsung DeX, starting with the new Galaxy Z Fold7 and Z Flip7, and also extend to the wider Android ecosystem.

To help you meet this moment, we’ve built a foundation of development tools to simplify creating compelling adaptive experiences. Create adaptive layouts that reflow automatically with the Compose Adaptive Layouts library and guide users seamlessly across panes with Jetpack Navigation 3. Make smarter top-level layout decisions using the newly expanded Window Size Classes. Then, iterate and validate your design in Android Studio, from visualizing your UI with Compose Previews to generating robust tests with natural language using Journeys with Gemini.

side by side images of Samsung's Watch8 Classic LTE 44mm in Silver on the left and Watch8 Classic LTE 46mm in Black on the right

Build for a more personal and expressive era with Wear OS 6

The next chapter for wearables begins with the new Samsung Galaxy Watch8 series becoming the first device to feature Wear OS 6, the most power-efficient version of our wearable platform yet. This update is focused on giving you the tools to create more personal experiences without compromising on battery life. With version 4 of the Watch Face Format, you can unlock new creative possibilities like letting users customize their watch faces by selecting their own photos or adding fluid transitions to the display. And, to give you more flexibility in distribution, the Watch Face Push API allows you to create and manage your own watch face marketplace.

Beyond the watch face, you can provide a streamlined experience to users by embracing an improved always-on display and adding passkey support to your app with the Credential Manager API, which is now available on Wear OS.

Check out the latest changes to get started and test your app for compatibility using the Wear OS 6 emulator.

Get started building across screens, from foldables to wearables

With these new devices from Samsung, there are more reasons than ever to build experiences that excite users on their favorite Android screens. From building fully adaptive apps for foldables to creating more personal experiences on Wear OS, the tools are in your hands to create for the future of Android.

Explore all the resources you’ll need to build adaptive experiences at developer.android.com/adaptive-apps. And, start building for Wear OS today by checking out developer.android.com/wear and visiting the Wear OS gallery for inspiration.

Google Ads API v18 Sunset Reminder

Google Ads API v18 will sunset on August 20, 2025. Starting on this date, all v18 API requests will begin to fail. Migrate to a newer version prior to August 20, 2025 to ensure your API access is unaffected.

Here are some resources to help you with the migration:

You can view a list of methods and services your project has recently called using the Google Cloud Console:

  1. Open the APIs & Services in the Google Cloud Console.
  2. Click Google Ads API in the table.
  3. On the METRICS subtab, you should see your recent requests plotted on each graph. You can see which methods you've sent requests to in the Methods table. The method name includes a Google Ads API version, a service, and a method name, such as google.ads.googleads.v18.services.GoogleAdsService.Mutate.
  4. (Optional) Choose the timeframe you want to view for your requests.

If you have questions while you’re upgrading, reach out to us on the forum or at [email protected].