Google Workspace Updates Weekly Recap – May 24, 2024

2 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.


Expanding row limits in Connected Sheets for BigQuery 
Last year, we increased the maximum number of rows of results returned from BigQuery to 50,000 for pivot tables and data extracts. This week, we’re excited to announce this has been expanded to 100,000 rows for pivot tables and 500,000 rows for extracts (with a cell limit of 5 million). This will allow you to analyze even more results in Sheets from the petabytes of data in BigQuery. | Rolling out to Rapid Release and Scheduled Release domains now. | Available to all Google Workspace customers, Workspace Individual Subscribers, and users with personal Google accounts. | Learn more about analyzing & refreshing BigQuery data in Google Sheets using Connected Sheets, Google Sheets limitations, and getting started with BigQuery data in Google Sheets.

Custom text fields are now available for eSignature in Google Docs and Google Drive 
You can now input custom text fields when using eSignature. This gives you the flexibility to collect specific information as needed, including a phone number, job title, company name, and more. | Available to Google Workspace Individual users and other eligible Google Workspace customers who are on the eSignature alpha. | Rolling out to Rapid Release domains and Scheduled Release domains now. | Learn more about sending signature requests & signing documents with eSignature.




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.


Filter, sort, and display your Google Meet hardware devices by product service status 
You can currently filter, sort, and display your Google Meet hardware devices by whether they are online, offline, or experiencing an application load-failure. This week, we’re expanding these parameters to include whether the Calendar and Jamboard services are turned OFF. | Learn more about filtering, sorting and displaying Meet hardware devices. 

Introducing adaptive audio in Google Meet: creating ad-hoc meeting spaces with multiple laptops 
With “adaptive audio,” you and your team can join Google Meet using multiple laptops in close proximity without awkward echos and audio feedback. | Learn more about adaptive audio in Google Meet. 

Send emails to spaces in Google Chat 
After a space manager generates an email address for a space, members (or anyone in your domain with the email address) can send or forward any email to that space. This provides a great way for teams to easily triage or discuss email content with stakeholders within the space. The email will appear as a clickable card showing a snippet of the email in the designated space. | Learn more about sending emails to spaces. 

Manage spaces at scale with new Chat API functionality 
We are pleased to announce the launch for additional features of Chat API via the Developer Preview Program, enabling space management at scale on behalf of admin users. These new features are available to all users currently enrolled in the Developer Preview Program. | Learn more about new Chat API functionality. 

Introducing Gemini offerings for Google Workspace for Education customers 
Beginning May 23, 2024, Google for Education customers will be able to leverage new and powerful ways of working, teaching and learning with Gemini for Google Workspace with two new paid add-ons. | Learn more about Gemini Education and Gemini Education Premium add-ons.

Expanding voice typing and automatic captions to additional browsers 
We’re expanding support for voice typing and captions features to additional browsers, such as Edge and Safari. When a user turns on voice typing or captions, the web browser controls the speech-to-text service, determines how speech is processed, and then sends text data to Google Docs and Google Slides. | Learn more about voice typing features in additional browsers.



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: 

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

Announcing v202405 of the Google Ad Manager API

We're pleased to announce that v202405 of the Google Ad Manager API is available today. This release brings support for contextual targeting.

It also includes a number of deprecations, such as the removal of the ActivityService, ActivityGroupService, and ACTIVITY reporting dimensions to support the Spotlight deprecation.

For the full list of changes, check the release notes. Feel free to contact us on the Ad Manager API forum with any API-related questions.

A Developer’s Roadmap to Predictive Back (Views)

Posted by Ash Nohe and Tram Bui – Developer Relations Engineers

Before you read on, this topic is scoped to Views. Predictive Back with Compose is easier to implement and not included in this blog post. To learn how to implement Compose with Predictive Back, see the Add predictive back animations codelab and the I/O workshop Improve the user experience of your Android app.

This blog post aims to shed light on various dependencies and requirements to support predictive back animations in your views based app.

First, view the Predictive Back Requirements table to understand if a particular animation requires a manifest flag, a compileSDK version, additional libraries or hidden developer options to function.

Then, start your quest. Here are your milestones:

  1. Upgrade Kotlin milestone
  2. Back-to-home animation milestone
  3. Migrate all activities milestone
  4. Fragment milestone
  5. Material Components (Views) milestone
  6. [Optional] AndroidX transitions milestone
Milestones

Upgrade Kotlin milestone

The first milestone is to upgrade to Kotlin 1.8.0 or higher, which is required for other Predictive Back dependencies.

Upgrade to Kotlin 1.8.0 or higher

Back-to-home animation milestone

The back-to-home animation is the keystone predictive back animation.

To get this animation, add android:enableOnBackInvokedCallback=true in your AndroidManifest.xml for your root activity if you are a multi-activity app (see per-activity opt-in) or at the application level if you are a single-activity app. After this, you’ll see both the back-to-home animation and a cross-task animation where applicable, which are visible to users in Android 15+ and behind a developer option in Android 13 and 14.

If you are intercepting back events in your root activity (e.g. MainActivity), you can continue to do so but you’ll need to use supported APIs and you won’t get the back-to-home animation. For this reason, we generally recommend you only intercept back events for UI logic; for example, to show a dialog asking the user to save before they quit.

See the Add support for the predictive back gesture guide for more details.

Milestone grid

Migrate all activities milestone

If you are a multi-activity app, you’ll need to opt-in and handle back events within those activities too to get a system controlled cross-activity animation. Learn more about per-activity opt-in, available for devices running Android 14+. The cross-activity animation is visible to users in Android 15+ and behind a developer option in Android 13 and 14.

Custom cross activity animations are also available with overrideActivityTransition.

Milestone grid

Fragment milestone

Next, you’ll want to focus on your fragment animations and transitions. This requires updating to AndroidX fragment 1.7.0 and transition 1.5.0 or later and using Animator or AndroidX Transitions. Assuming these requirements are met, your existing fragment animations and transitions will animate in step with the back gesture. You can also use material motion with fragments. Most material motions support predictive back as of 1.12.02-alpha02 or higher, including MaterialFadeThrough, MaterialSharedAxis and MaterialFade.

Don’t strive to make your fragment transitions look like the system’s cross-activity transition. We recommend this full screen surface transition instead.

Learn more about Fragments and Predictive Back.

Milestone grid

Material Components milestone

Finally, you’ll want to take advantage of the Material Component View animations available for Predictive Back. Learn more about available components.

Milestone grid

After this, you’ve completed your quest to support Predictive Back animations in your view based app.

[Optional] AndroidX Transitions milestone

If you’re up for more, you might also ensure your AndroidX transitions are supported with Predictive Back. Read more about AndroidX Transitions and the Predictive Back Progress APIs.

Milestone grid

Other Resources

Chrome Dev for Android Update

Hi everyone! We've just released Chrome Dev 127 (127.0.6493.0) 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