Google Classroom now supports exporting grades and importing rosters and grade settings with PowerSchool SIS

What’s changing

Google Classroom teachers can now export and import select information via the new integration with PowerSchool SIS, a third-party student information system (SIS) that provides innovative K-12 software and cloud-based solutions to improve educational outcomes and simplify school operations. 

Once an admin establishes a connection between PowerSchool SIS and Classroom, teachers will be able to export grades from Classroom to PowerTeacher Pro Gradebook. Teachers can also import useful information, such as student rosters, co-teachers and grading categories, from PowerSchool SIS into Classroom. 
Classroom integration with PowerSchool SIS



Getting started 

Rollout pace 

  • This feature is available now 

Availability 

Available for Google Workspace: 
  • Education Plus and the Teaching & Learning Upgrade 

Resources 

Google Workspace Updates Weekly Recap – July 12, 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.


Shared drives can now have up to 100 levels of nested folders and 500,000 items 
Prior to this month, a folder in a shared drive could have up to 20 levels of nested folders and could contain a maximum of 400,000 items. Today, we’re excited to announce that we’ve increased the nested folder limit to 100 levels and the maximum number of items to 500,000. | Rollout to Rapid and Scheduled Release domains is complete. | Available to Google Workspace customers, Google Workspace Individual subscribers, and users with personal Google accounts. | Learn more about shared drive limits in Google Drive. 

eSignature is now available for select Google Workspace customers 
As previously announced, starting July 15, 2024, we will begin rolling out eSignature for Google Docs to end users on select Google Workspace editions. eSignature offers a variety of features to help you streamline requesting and capturing signatures, helping you stay organized and keep your work moving along. Specifically, you can: 
  • Request eSignatures, including signatures from more than one user and from non-Gmail users. 
  • View the status of pending signatures and find completed contracts. 
  • Keep contract templates to initiate multiple eSignature requests. 
  • View an audit trail of completed contracts.
  • Use custom text fields to request additional information from signers, such as job titles, email addresses and more. 
  • Sign contracts from both mobile devices and PCs. 
Rollout to Rapid and Scheduled Release domains starts July 15, 2024 at a gradual pace (up to 15 days for feature visibility). | Available to Google Workspace Business Standard, Business Plus, Enterprise Starter, Enterprise Standard, Enterprise Plus, Enterprise Essentials, Enterprise Essentials Plus, and Education Plus customers. | Learn more about sending signature requests & sign 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.


Introducing a new experience for data regions reporting
We’ve introduced several new enhancements to Google Workspace data regions. | Learn more about data regions reporting. 

Access Management is now generally available in the European Union 
Access Management is now also generally available in the European Union — these controls allow customers to select the physical location from which Google support teams can access organizational data during support activities. | Learn more about Access Management. 

Manage your compliance and data controls from a single source in the Admin console 
We’ve centralized relevant features and information into a single location in the admin console: Data. | Learn more about compliance and data controls. 

Enhancing the Google Calendar appointment scheduling experience with additional feature
We’re updating appointment schedules by adding new features to enhance the overall experience. | Learn more about appointment scheduling updates. 

Pre-configure meeting notes, recordings, and transcripts from the Calendar invite 
Meeting hosts can now pre-configure meeting notes, meeting recordings, and meeting transcripts from the Calendar invite. | Learn more about meeting host capabilities. 

Use the Apple Volume Purchasing Program (VPP) to distribute apps for device enrollment and company owned devices 
In November 2023, we announced the ability to purchase and distribute iOS apps to user-enrolled devices through Apple’s Volume Purchase Program. Beginning this week, we’re expanding this functionality to include device enrollment and company-owned iOS devices. | Learn more about the Apple Volume Purchasing Program. 

Google Meet and Zoom interoperability now includes presented content via a wired HDMI connection 
We’re expanding the interoperability between Google Meet and Zoom to include the ability to present content via a wired HDMI connection. | Learn more about Google Meet and Zoom interoperability.

Rollout Update: setting the default camera framing option for Google Meet hardware devices
We recently announced several updates related to framing options on Google Hardware devices. This included the ability for admins to configure the default camera framing option for their hardware devices. After pausing rollout to optimize performance, we are pleased to announce that this feature is now fully available. | Learn more about default camera framing options for Meet hardware devices.

Access Google Meet artifacts with a new Google Drive API scope
We’re introducing a new OAuth scope for the Drive API: drive.meet.readonly. The new scope grants app access to read and download files from a user’s drive that were created or edited by Google Meet — this includes meeting transcripts, notes, recordings, and more. | Learn more about accessing Meet artifacts.


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.



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

Prepare your app for the new Samsung Galaxy foldables and watches!

Posted by Maru Ahues Bouza – Product Management Director, Android Developer

Yesterday’s Galaxy Unpacked event from Samsung debuted the latest in foldables, wearables, and more! The event introduced the Galaxy Z Fold6 and Z Flip6 and the Galaxy Watch7 and Watch Ultra - and it has never been easier to build apps that look great across all these screen sizes and types. To help you get your apps ready for the latest Android devices, we’re sharing how you can prepare your app for Wear OS 5 and how to build adaptive apps that scale across mobile, tablets, foldables and more!

Get your app ready for Wear OS 5

Samsung’s new Galaxy Watch lineup, including the Watch Ultra and Watch7, will be the first smartwatches powered by Wear OS 5, the latest version of the Wear OS platform. As Wear OS 5 is based on Android 14, this new platform version brings with it a number of developer-facing changes. To ensure your app is ready for the next generation of devices, start by testing your app on the Wear OS 5 Emulator!

Galaxy Watch Ultra (left) and Galaxy Watch7 (right)
Galaxy Watch Ultra (left) and Galaxy Watch7 (right)

Wear OS 5 brings the next iteration of the Watch Face Format, providing more features to create expressive, efficient and individual watch faces for your users. New watches launched with Wear OS 5 will only support third-party watch faces built with Watch Face Format, prioritizing the user experience. For more information on watch face compatibility, see this Help Center article.

As we gather momentum behind the Watch Face Format, we’re changing requirements for publishing watch faces on Google Play. Check out the watch face page for the latest guidance.

Build adaptive to scale across screen sizes and types

The latest in large screens and foldables are here, with the new Galaxy Z Fold6 and Z Flip6, so there is even more reason to ensure your app looks great across whatever screen size or folded state your users are engaging with. The best way to do that is to make your app adaptive - meaning your users get an optimal experience on all their devices. By building an adaptive app, you scale across mobile, tablets, foldables, desktop and more.

Galaxy Watch Ultra (left) and Galaxy Watch7 (right)
Galaxy Z Fold6

A great place to start when building adaptive apps is with the new Compose adaptive layout libraries. These libraries are designed to help you to make your UI look good across window sizes. From navigation UI to list/detail and supporting pane layouts, we’re providing composables to make building an adaptive app easier than ever.

Additionally, window size classes are the best way to scale your UI, with opinionated breakpoints that help you design, develop, and test responsive/adaptive layouts across various window sizes. Window size classes enable you to change your app layout as the display space available to your app changes, for example, when a device folds or unfolds, the device orientation changes, or the app window is resized in multi‑window mode.

Discover everything you need to know about building adaptive apps with the adaptive apps documentation; it will be continually updated with the latest and greatest tools and APIs to enable you to scale across screens!

Get started with Adaptive Apps and Wear OS

With these new devices, from the smallest to the largest, there are opportunities to build apps that excite your users on all their favorite Android screens. Apps like SoundCloud, Peloton, and more are already building experiences that scale across their user’s favorite screens!

Get building for Wear OS today by checking out Wear OS developer site and visiting the Wear OS gallery for inspiration. And scale your app across even more screens by building adaptive with the latest from Compose!

Chrome Dev for Desktop Update

The Dev channel has been updated to 128.0.6585.0 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.

Prudhvi Bommana
Google Chrome

Access Google Meet artifacts with a new Google Drive API scope

What’s changing 

We’re introducing a new OAuth scope for the Drive API: drive.meet.readonly. The new scope grants app access to read and download files from a user’s drive that were created or edited by Google Meet — this includes meeting transcripts, notes, recordings, and more. This granular level of authorization helps ensure Drive access is not provisioned too broadly and only the necessary files can be accessed.


Getting started

Rollout pace


Availability


Reminder: Entity Read Files sunset on October 31, 2024

On October 31, 2024, Display & Video 360 Entity Read Files (ERFs) will sunset. After this date, new private and public ERFs will not be generated. ERFs were deprecated in June 2021 and the October sunset date was first announced in January 2024.

If you are currently using ERFs to programmatically retrieve Display & Video 360 resource configurations, migrate to the Display & Video 360 API. You can either integrate directly with the Display & Video 360 API using REST requests or automatically import Display & Video 360 resource configurations into BigQuery using the Display & Video 360 API BigQuery Connector.

See our migration guide for more information on migrating to the Display & Video 360 API and the two integration options.

If you have questions or concerns about this migration, please contact us using our new Display & Video 360 API Technical support contact form.

Reduce ANRs when implementing mobile ads

We heard your feedback via Play Console crash reports regarding Application Not Responding (ANRs) errors related to the Google Mobile Ads SDK. After analyzing these reports, we updated our SDK implementation best practices to reduce ANR rates. The recommended best practices are as follows:

  1. Initialize the Mobile Ads SDK on a background thread
  2. Enable optimization flag for ad loading

1. Initialize the Mobile Ads SDK on a background thread

Our previous best practice was to specify the OPTIMIZE_INITIALIZATION manifest flag. However, some work on the calling thread is still required to prepare MobileAds to handle other method calls synchronously.

We now recommend calling MobileAds.initialize() on a background thread, enabling the work required on the calling thread to happen in the background.

import com.google.android.gms.ads.MobileAds
import kotlinx.coroutines.CoroutineScope
import kotlinx.coroutines.Dispatchers
import kotlinx.coroutines.launch

class MainActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_main)

    CoroutineScope(Dispatchers.IO).launch {
      // Initialize the Google Mobile Ads SDK on a background thread.
      MobileAds.initialize(this@MainActivity) {}
      runOnUiThread {
        // Load an ad on the main thread.
        loadAd()
      }
    }
  }
}

Note: When calling MobileAds.initialize() on a background thread, the OPTIMIZE_INITIALIZATION manifest flag is no longer required.

2. Enable optimization flag for ad loading

By enabling the OPTIMIZE_AD_LOADING manifest flag, you can offload most ad loading tasks to a background thread. We recommend enabling this flag in your app's AndroidManifest.xml file to reduce the occurrence of ad loading causing ANRs.

<manifest>
  ...
  <application>
      ...
      <meta-data
          android:name="com.google.android.gms.ads.flag.OPTIMIZE_AD_LOADING"
          android:value="true"/>
  </application>
</manifest>

We’ve updated all of our Android example apps to implement these best practices. For more details on initialization and optimization flags, see Get started and Optimize initialization and ad loading. Contact us if you have any questions or need additional help.