Tag Archives: Beta

Available in beta: automatically log Google Voice calls made to Salesforce contacts

What’s changing 

Launching in beta, we’re introducing an integration between Google Voice and Salesforce that makes it easier to track details of calls made in Voice. When enabled: 

  • Salesforce contacts will be displayed in Google Voice. 
  • Google Voice calls will now be logged to any matching Salesforce contact.

Salesforce contacts are denoted with the Salesforce logo. 




Who’s impacted


Admins and end users


Why you’d use it


This integration helps improve visibility across the various stakeholders that rely on Salesforce as a key tool in their workflow. When enabled, Google Voice calls will be automatically logged in Salesforce, ensuring that there is a record of that interaction for all to see. Additionally, you can jump from Google Voice to the Salesforce call log to add notes and more context. This helps eliminate the need for users to switch between multiple applications and manual record keeping, and make it easier for other team members to see the latest activity in Salesforce.

Getting started



To turn on the Google Voice and Salesforce integration, navigate to Apps > Google Workspace > Google Voice > Policies > Salesforce integration


You’ll then be directed to the Google Voice and Salesforce connection page to complete the set-up.


  • End users: You’ll see banners in Google Voice on web and mobile when this integration is enabled by your admin. 
Banners inside the Voice app will indicate when Salesforce has been integrated.






After you make a Voice Call to a Salesforce contact from either our web or mobile app, you will be notified that the call is logged to Salesforce in the call log.

You’ll see when a call has been logged to Salesforce — you can click on this notification to open Salesforce.

Logged calls within the Salesforce UI.


To make the most out of the integration, we recommend that you install the Google Voice Chrome Extension.

Rollout pace

  • We will be accepting beta applications for this feature over the next several weeks. You can expect to hear back on the status of your beta application in about 2-3 business days.

Availability

  • Available to Google Workspace customers with Voice Standard or Premier and Salesforce Enterprise, Unlimited, or Lightning versions

Resources






The First Beta of Android 15

Posted by Dave Burke, VP of Engineering

Android 14 logo


Today we're releasing the first beta of Android 15. With the progress we've made refining the features and stability of Android 15, it's time to open the experience up to both developers and early adopters, so you can now enroll any supported Pixel device here to get this and future Android 15 Beta and feature drop Beta updates over-the-air.

Android 15 continues our work to build a platform that helps improve your productivity, give users a premium app experience, protect user privacy and security, and make your app accessible to as many people as possible — all in a vibrant and diverse ecosystem of devices, silicon partners, and carriers.

Android delivers enhancements and new features year-round, and your feedback on the Android beta program plays a key role in helping Android continuously improve. The Android 15 developer site has lots more information about the beta, including downloads for Pixel and the release timeline. We’re looking forward to hearing what you think, and thank you in advance for your continued help in making Android a platform that works for everyone.

We’ll have lots more to share as we move through the release cycle, and be sure to tune into Google I/O where you can dive deeper into topics that interest you with over 100 sessions, workshops, codelabs, and demos.

Edge-to-edge

Apps targeting Android 15 are displayed edge-to-edge by default on Android 15 devices. This means that apps no longer need to explicitly call Window.setDecorFitsSystemWindows(false) or enableEdgeToEdge() to show their content behind the system bars, although we recommend continuing to call enableEdgeToEdge() to get the edge-to-edge experience on earlier Android releases.

To assist your app with going edge-to-edge, many of the Material 3 composables handle insets for you, based on how the composables are placed in your app according to the Material specifications.

a side-by-side comparison of App targets SDK 34 (left) and App targets SDK 35 (right) demonstrating edge-to-edge on an Android 15 device
On the left: App targets SDK 34 (Android 14) and is not edge-to-edge on an Android 15 device. On the right: App targets SDK 35 (Android 15) and is edge-to-edge on an Android 15 device. Note the Material 3 TopAppBar is automatically protecting the status bar, which would otherwise be transparent by default.

The system bars are transparent or translucent and content will draw behind by default. Refer to "Handle overlaps using insets" (Views) or Window insets in Compose to see how to prevent important touch targets from being hidden by the system bars.

Smoother NFC experiences - part 2

Android 15 is working to make the tap to pay experience more seamless and reliable while continuing to support Android's robust NFC app ecosystem. In addition to the observe mode changes from Android 15 developer preview 2, apps can now register a fingerprint on supported devices so they can be notified of polling loop activity, which allows for smooth operation with multiple NFC-aware applications.

Inter-character justification

Starting with Android 15, text can be justified utilizing letter spacing by using JUSTIFICATION_MODE_INTER_CHARACTER. Inter-word justification was first introduced in Android O, but inter-character solves for languages that use the white space for segmentation, e.g. Chinese, Japanese, etc.

JUSTIFICATION_MODE_NONE
image shows how japanese kanji (top) and english alphabet characters (bottom) appear with JUSTIFICATION_MODE_NONE
JUSTIFICATION_MODE_INTER_WORD
image shows how japanese kanji (top) and english alphabet characters (bottom) appear with JUSTIFICATION_MODE_INTER_WORD
JUSTIFICATION_MODE_INTER_CHARACTER
image shows how japanese kanji (top) and english alphabet characters (bottom) appear with JUSTIFICATION_MODE_INTER_WORD

App archiving

Android and Google Play announced support for app archiving last year, allowing users to free up space by partially removing infrequently used apps from the device that were published using Android App Bundle on Google Play. Android 15 now includes OS level support for app archiving and unarchiving, making it easier for all app stores to implement it.

Apps with the REQUEST_DELETE_PACKAGES permission can call the PackageInstaller requestArchive method to request archiving a currently installed app package, which removes the APK and any cached files, but persists user data. Archived apps are returned as displayable apps through the LauncherApps APIs; users will see a UI treatment to highlight that those apps are archived. If a user taps on an archived app, the responsible installer will get a request to unarchive it, and the restoration process can be monitored by the ACTION_PACKAGE_ADDED broadcast.

App-managed profiling

Android 15 includes the all new ProfilingManager class, which allows you to collect profiling information from within your app. We're planning to wrap this with an Android Jetpack API that will simplify construction of profiling requests, but the core API will allow the collection of heap dumps, heap profiles, stack sampling, and more. It provides a callback to your app with a supplied tag to identify the output file, which is delivered to your app's files directory. The API does rate limiting to minimize the performance impact.

Better Braille

In Android 15, we've made it possible for TalkBack to support Braille displays that are using the HID standard over both USB and secure Bluetooth.

This standard, much like the one used by mice and keyboards, will help Android support a wider range of Braille displays over time.

Key management for end-to-end encryption

We are introducing the E2eeContactKeysManager in Android 15, which facilitates end-to-end encryption (E2EE) in your Android apps by providing an OS-level API for the storage of cryptographic public keys.

The E2eeContactKeysManager is designed to integrate with the platform contacts app to give users a centralized way to manage and verify their contacts' public keys.

Secured background activity launches

Android 15 brings additional changes to prevent malicious background apps from bringing other apps to the foreground, elevating their privileges, and abusing user interaction, aiming to protect users from malicious apps and give them more control over their devices. Background activity launches have been restricted since Android 10.

App compatibility

With Android 15 now in beta, we're opening up access to early-adopter users as well as developers, so if you haven't yet tested your app for compatibility with Android 15, now is the time to do it. In the weeks ahead, you can expect more users to try your app on Android 15 and raise issues they find.

To test for compatibility, install your published app on a device or emulator running Android 15 beta and work through all of your app's flows. Review the behavior changes to focus your testing. After you've resolved any issues, publish an update as soon as possible.

To give you more time to plan for app compatibility work, we’re letting you know our Platform Stability milestone well in advance.

Android 15 release timeline

At this milestone, we’ll deliver final SDK/NDK APIs and also final internal APIs and app-facing system behaviors. We’re expecting to reach Platform Stability in June 2024, and from that time you’ll have several months before the official release to do your final testing. The release timeline details are here.

Get started with Android 15

Today's beta release has everything you need to try the Android 15 features, test your apps, and give us feedback. Now that we've entered the beta phase, you can enroll any supported Pixel device here to get this and future Android Beta updates over-the-air. If you don’t have a Pixel device, you can use the 64-bit system images with the Android Emulator in Android Studio. If you're already in the Android 14 QPR beta program on a supported device, or have installed the developer preview, you'll automatically get updated to Android 15 Beta 1.

For the best development experience with Android 15, we recommend that you use the latest version of Android Studio Jellyfish (or more recent Jellyfish+ versions). Once you’re set up, here are some of the things you should do:

    • Try the new features and APIs - your feedback is critical during the early part of the developer preview and beta program. Report issues in our tracker on the feedback page.
    • Test your current app for compatibility - learn whether your app is affected by changes in Android 15; install your app onto a device or emulator running Android 15 and extensively test it.

We’ll update the beta system images and SDK regularly throughout the Android 15 release cycle. Read more here.

For complete information, visit the Android 15 developer site.


Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.

Migrate email data from one Google Workspace account to another, available in open beta

What’s changing

Beginning today, a new data migration experience is available: you can migrate your users’ email data from one Google Workspace account to another in a more reliable and efficient manner. You can configure your data migration for up to 100 users at a time and also run delta migrations, which smartly brings over any newly generated data from the source without duplicating previously migrated content.

This feature is available as an open beta, which means admins can use it without enrolling in a specific beta program.


Additional details

You can find more information in our Help Center about migrating other forms of data from different types of source accounts.

Getting started

  • Admins: Visit The Help Center to learn more about the new data migration service and migrating email.
  • End users: There is no end user action required


Rollout pace

  • This feature is available now in open beta.

    Availability

    • Available to Google Workspace Business Starter, Business Standard, and Business Plus; Enterprise Standard and Enterprise Plus; Education Fundamentals, Education Standard, Teaching and Learning Upgrade, and Education Plus; Essentials Starter, Essentials, Enterprise Essentials, and Enterprise Essentials Plus, and Nonprofits customers

      Resources

        Available in open beta: the Groups Admin role can now be provisioned for specific group types

        What’s changing

        The Groups Admin role can now be assigned for security groups or non-security groups. Previously, those with the Groups Admin role had access to all groups within an organization. This change gives administrators more granular delegation of group admin responsibilities, helping limit access to the most sensitive groups to only those who absolutely need it. 

        This feature is available in open beta, which means no additional sign-up is required to use the feature.

        Getting started

        Assign mobile device management admin privileges based on organizational unit

        What’s changing

        We’re giving admins more granular control over how mobile device management privileges are delegated. Specifically, admins can be assigned privileges for specific organizational units (OUs). This adds yet another layer of security by ensuring that access is scoped to the necessary OUs only. This feature is available as an open beta, which means you can use it without enrolling in a specific beta program.


        Creating a custom role, which is assignable at the OU level.

        Assigning permissions at the OU level




        Example experience for an admin with OU level permissions





        Getting started


        Rollout pace


        Availability

        • Available to all Google Workspace customers

        Resources


        Assign mobile device management admin privileges based on organizational unit

        What’s changing

        We’re giving admins more granular control over how mobile device management privileges are delegated. Specifically, admins can be assigned privileges for specific organizational units (OUs). This adds yet another layer of security by ensuring that access is scoped to the necessary OUs only. This feature is available as an open beta, which means you can use it without enrolling in a specific beta program.


        Creating a custom role, which is assignable at the OU level.

        Assigning permissions at the OU level




        Example experience for an admin with OU level permissions





        Getting started


        Rollout pace


        Availability

        • Available to all Google Workspace customers

        Resources


        eSignature is now generally available for Google Workspace Individual subscribers

        What’s changing 

        Earlier this year, we introduced eSignature for Docs and Drive in beta. Today, eSignature for Docs and Drive is rolling out in general availability for all Workspace Individual customers. 


        Built directly into Google Docs, eSignature makes it easier for solopreneurs and small businesses to request signatures, keep track of and manage contracts like customer agreements, vendor contracts, stakeholder sign-offs and more. eSignature can be used to: 
        • Request signatures, see the status of pending signatures, and find completed contracts. 
        • Sign official contracts directly within Google Drive, eliminating the need to switch apps or tabs. 
        • Create a copy of any given contract so it can be used as a template to initiate multiple eSignatures requests.



        Since the last announcement, we’ve expanded functionality to include the following features:
        • Audit trail: all completed contracts will automatically contain an audit trail report.
        • Multi-signer: the ability to request a signature from more than one user.
        • Non-Gmail users: the ability to request an eSignature from non-Gmail users.
        • Initiating eSignature on PDF (beta): the ability to initiate an eSignature on PDF files stored in Drive.

        We’ll also be introducing more features for eSignature in the next few months, including:
        • PDF templates: the ability to easily reuse a PDF file as contract templates.
        • Custom text fields: the ability to ask signers to add relevant information (e.g. job titles, email address) to the contract. 


        Additional details

        Select Google Workspace editions (see the “Availability” section below) can apply to beta test eSignature using this form. We will be accepting beta applications until December 18, 2023.


        This feature will be available as part of a larger beta, which includes access to new custom email layouts in Gmail. These new email layouts allow users to customize existing templates, reuse a custom layout in multiple email campaigns, or create a brand new layout from scratch. Once you sign up for the beta you will see the eSignature and new Gmail features in the coming weeks.

        Getting started


        Rollout pace


        Availability

        • Available to Google Workspace Individual Subscribers 

        • Eligible for beta: Google Workspace Business Standard, Business Plus, Enterprise Starter, Enterprise Standard, Enterprise Plus, Enterprise Essentials, Enterprise Essentials Plus, Education Plus, and Nonprofits customers

        Resources


        Beta Channel Update for ChromeOS / ChromeOS Flex

        Hello All,

        The Beta channel has been updated to 120.0.6099.80 (Platform version: 15662.35.0) for ChromeOS devices.

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

        Interested in switching channels? Find out how.


        Google ChromeOS

        Beta Channel Release for ChromeOS / ChromeOS Flex

        Hello All,

        The Beta channel has been updated to 120.0.6099.25 (Platform version: 15662.16.0) for ChromeOS devices.

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

        Interested in switching channels? Find out how.


        Google ChromeOS

        Beta Channel Release for ChromeOS / ChromeOS Flex

        Hello All,

        The Beta channel has been updated to 120.0.6099.25 (Platform version: 15662.16.0) for ChromeOS devices.

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

        Interested in switching channels? Find out how.


        Google ChromeOS