Review smart home devices used for work in your Admin console

What’s changing

Admins can now view and manage the smart displays and speakers that access work data in the Admin console, alongside other devices managed with Google endpoint management



Who’s impacted 

Admins 


Why it’s important 

In addition to computers and mobile devices, the inclusion of smart displays and speakers in Google endpoint management gives admins a more complete inventory of the devices their users are using to access Google Workspace. Further, this allows admins to easily take action if needed, such as signing out of devices as needed and viewing information such as device type and user account information. 


Additional details 

For select Google Workspace editions, admins can view activity on smart home devices as part of device audit logs. You’ll be able to see information such as: 
  • Whether there has been an account registration change, 
  • If a user’s managed account synced on the device, 
  • If the device has been signed out by an admin. 

You can also set an alert to be notified when these activities occur. Visit the Help Center to learn more about device audit logs


Getting started 


Rollout pace 


Availability 

  • Available to all Google Workspace customers, as well as G Suite Basic and Business customers 

Resources 

Introducing the Flutter Meetup Network!

Posted by Sarah Fullmer, Program Manager

Image of three blue Flutter birds

The Flutter Meetup Network (FMN) is an international network of Meetup groups united by their enthusiasm for Flutter. The FMN program mission is to foster a thriving worldwide community of Flutter developers by empowering community organizers to educate and inspire local communities with engaging events.

Meetups – and similar developer community groups - are a great resource. As Flutter has grown in popularity over the past few years, over 100 Meetup groups have sprung up organically around the world to celebrate and educate their members about Flutter. The volunteers who run these groups have hosted many awesome events and workshops.

Image of world map showing Flutter Meetup opportunities. Shows 102 groups across 52 countries

We, in the Flutter team, see and appreciate these amazing communities. ? The Flutter Meetup Network (FMN) is now being launched to support these groups officially. Network members will have access to various resources (more details available soon!), making it easier to plan and host Flutter-themed events.

Meetups have many benefits, aside from networking. When stuck on an issue in your current Flutter project, chances are good that you can find a developer in your local Flutter Meetup who has solved a similar problem. Or, maybe they know the perfect package for your needs.

We are thrilled to support our amazing and passionate organizers and can’t wait to see what the Flutter Meetup Network does moving forward.

Join a Meetup near you! https://www.meetup.com/pro/flutter

Answering your top questions on Android Game Development Kit

Posted by Wayne Lu, Technical Lead Manager, Android DevRel

hand holding a phone with game and chat

We launched the Android Game Development Kit (AGDK) in July, and have collected some top questions from developers - ranging from AGDK libraries and tools, optimizing memory in Android, and implementing graphics.


AGDK and game engines

Firstly, we’ve heard questions from early, rising game developers on how to use our set of AGDK libraries and tools. We have the following recommendations depending on your setup:

  1. For game developers using popular game engines such as Defold, Godot, Unity, or Unreal - you can follow our guides to learn how to develop apps on Android. Using these game engines lets you focus on building gameplay instead of the entire technology stack.
  2. If you're using Unreal Engine and targeting multiple platforms such as PC or consoles, Android Game Development Extension (AGDE) may be a great addition to your workflow.
  3. We also support developers who want to customize and write their own game engine - you can learn more about this with our C or C++ documentation.

After choosing your game engine and workflow, you should look into our tools such as the Android Studio Profiler to inspect your game, Android GPU Inspector to profile graphics and Android Performance Tuner to optimize frame rates and loading times.


Game Mode API and Interventions

Following this, we’ve received questions on developing for Android 12. While you don’t have to do anything special for your game to run on Android 12, we’ve introduced Game Mode API and interventions to help players customise their gaming experience.

  1. Read more about the Game Mode API, and find out how to optimize your game for the best performance or longest battery life when the user selects the corresponding game mode.
  2. Learn about the Game Mode interventions - these are set by original equipment manufacturers (OEMs), to improve the performance of games that are no longer being updated by developers. For example: WindowManager backbuffer resize to reduce a device's GPU load.

Memory Access in Android

Secondly, you’ve asked us how memory access works in Android game development versus Windows. In short, here are a couple of pointers:

  1. Games need to share memory with the system. Some devices have less available memory than others, so testing is needed to check for low memory issues on a range of supported devices. Testing should be done on devices with typical apps that a user would have installed (i.e. not a clean device).
  2. The amount of memory a game can allocate depends on various factors such as the amount of physical memory, the number of dirty pages, and the amount of total zRam (for compressed swapping)
  3. Symptoms of low memory can be: onTrimMemory() calls, memory thrashing, or termination of the game by the Low Memory Killer. Use bugreport logs to check if the game was killed by the Low Memory Killer, or on Android 11 and later check the ApplicationExitInfo to see if the game was terminated because of REASON_LOW_MEMORY.
  4. Avoid memory thrashing: this occurs when there’s low but insufficient memory to kill the game. You can detect this via system tracing, and should reduce the overall memory footprint to avoid this issue.
  5. Use the Android Profiler and other tools to inspect your memory usage.

Implementing Graphics in Android

Thirdly, we’ve received questions about implementing graphics in Android. You have the following options: OpenGL ES or Vulkan graphics APIs:

  1. Learn how to configure OpenGL ES graphics for your C++ game engine by initializing variables, rendering with the game loop, scenes and objects.
  2. Read our Vulkan guides to learn how to draw a cube, compile shaders, setup validation layers, and other best practices.

Check out the Q&A video to view the top questions on AGDK and visit g.co/android/AGDK for our latest resources for Android game development.

Google Ads API, Google Ads scripts, and AdWords API issues on Oct 1

Between 2:50 am EDT and 6:40 am EDT on October 1, there was an outage that may have prevented some users from accessing the Google Ads API, Google Ads scripts, & the AdWords API. If you were using the Google Ads API or the AdWords API or running Google Ads scripts, then you may have experienced slowness or timeouts. Please check for any failed requests from these tools during the outage.

If you have any questions, please contact us via the forum.

Use the “Slideshow” button in Google Slides

Quick launch summary

We’re replacing what was previously the “Present” button in Slides to now say “Slideshow.” We hope this makes it clearer when you are beginning a slide show, and when you are sharing your screen in Meet.
New "Slideshow" button in Slides

"Present" button which formerly would begin a slideshow in Slides
Old "Present" button in Slides


Getting started

  • Admins: There is no admin control for this feature.
  • End users: There is no end user setting for this feature.

Rollout pace


Availability

  • Available to all Google Workspace customers, as well as G Suite Basic and Business customers

 

Use the “Slideshow” button in Google Slides

Quick launch summary

We’re replacing what was previously the “Present” button in Slides to now say “Slideshow.” We hope this makes it clearer when you are beginning a slide show, and when you are sharing your screen in Meet.
New "Slideshow" button in Slides

"Present" button which formerly would begin a slideshow in Slides
Old "Present" button in Slides


Getting started

  • Admins: There is no admin control for this feature.
  • End users: There is no end user setting for this feature.

Rollout pace


Availability

  • Available to all Google Workspace customers, as well as G Suite Basic and Business customers

 

Use the “Slideshow” button in Google Slides

Quick launch summary

We’re replacing what was previously the “Present” button in Slides to now say “Slideshow.” We hope this makes it clearer when you are beginning a slide show, and when you are sharing your screen in Meet.
New "Slideshow" button in Slides

"Present" button which formerly would begin a slideshow in Slides
Old "Present" button in Slides


Getting started

  • Admins: There is no admin control for this feature.
  • End users: There is no end user setting for this feature.

Rollout pace


Availability

  • Available to all Google Workspace customers, as well as G Suite Basic and Business customers

 

Introducing the Secure Open Source Pilot Program


Over the past year we have made a number of investments to strengthen the security of critical open source projects, and recently announced our $10 billion commitment to cybersecurity defense including $100 million to support third-party foundations that manage open source security priorities and help fix vulnerabilities.

Today, we are excited to announce our sponsorship for the Secure Open Source (SOS) pilot program run by the Linux Foundation. This program financially rewards developers for enhancing the security of critical open source projects that we all depend on. We are starting with a $1 million investment and plan to expand the scope of the program based on community feedback.


Why SOS?

SOS rewards a very broad range of improvements that proactively harden critical open source projects and supporting infrastructure against application and supply chain attacks. To complement existing programs that reward vulnerability management, SOS’s scope is comparatively wider in the type of work it rewards, in order to support project developers.


What projects are in scope?

Since there is no one definition of what makes an open source project critical, our selection process will be holistic. During submission evaluation we will consider the guidelines established by the National Institute of Standards and Technology’s definition in response to the recent Executive Order on Cybersecurity along with criteria listed below:
  • The impact of the project:
    • How many and what types of users will be affected by the security improvements?
    • Will the improvements have a significant impact on infrastructure and user security?
    • If the project were compromised, how serious or wide-reaching would the implications be?
  • The project’s rankings in existing open source criticality research:

What security improvements qualify? 

The program is initially focused on rewarding the following work:

  • Software supply chain security improvements including hardening CI/CD pipelines and distribution infrastructure. The SLSA framework suggests specific requirements to consider, such as basic provenance generation and verification.
  • Adoption of software artifact signing and verification. One option to consider is Sigstore's set of utilities (e.g. cosign).
  • Project improvements that produce higher OpenSSF Scorecard results. For example, a contributor can follow remediation suggestions for the following Scorecard checks:
    • Code-Review
    • Branch-Protection
    • Pinned-Dependencies
    • Dependency-Update-Tool
    • Fuzzing
  • Use of OpenSSF Allstar and remediation of discovered issues.
  • Earning a CII Best Practice Badge (which also improves the Scorecard results).
We'll continue adding to the above list, so check our FAQ for updates. You may also submit improvements not listed above, if you provide justification and evidence to help us understand the complexity and impact of the work.

Only work completed after October 1, 2021 qualifies for SOS rewards.

Upfront funding is available on a limited case by case basis for impactful improvements of moderate to high complexity over a longer time span. Such requests should explain why funding is required upfront and provide a detailed plan of how the improvements will be landed.

How to participate

Review our FAQ and fill out this form to submit your application.

Please include as much data or supporting evidence as possible to help us evaluate the significance of the project and your improvements. 


Reward amounts

Reward amounts are determined based on complexity and impact of work:
  • $10,000 or more for complicated, high-impact and lasting improvements that almost certainly prevent major vulnerabilities in the affected code or supporting infrastructure.
  • $5,000-$10,000 for moderately complex improvements that offer compelling security benefits.
  • $1,000-$5,000 for submissions of modest complexity and impact.
  • $505 for small improvements that nevertheless have merit from a security standpoint.

Looking Ahead

The SOS program is part of a broader effort to address a growing truth: the world relies on open source software, but widespread support and financial contributions are necessary to keep that software safe and secure. This $1 million investment is just the beginning—we envision the SOS pilot program as the starting point for future efforts that will hopefully bring together other large organizations and turn it into a sustainable, long-term initiative under the OpenSSF. We welcome community feedback and interest from others who want to contribute to the SOS program. Together we can pool our support to give back to the open source community that makes the modern internet possible.

Support for African startup founders looking to scale

One of the top challenges we hear from startup founders around the world—and from African entrepreneurs in particular— is how difficult it can be to acquire new customers and partners when you’re getting started. Google believes that equipping founders with critical sales skills at the beginning of their journey is the best way to build confidence and skills for lasting success. So we created the Google for Startups Sales Academy to provide Sub-Saharan startup founders with essential sales skills and practices that they can implement immediately to acquire new customers and partnerships, and secure funding.

Over the course of seven weeks, 15 founders from Ghana, Uganda, Kenya and South Africa engaged in tactical training sessions with Google mentors and industry experts designed to help them establish a solid foundation for increasing their revenue. During the final week of programming in September, founders perfected their mock sales pitch to earn an official Google for Startups sales certification. The results speak for themselves: 100% of the cohort reported an increase in their confidence and closing skills after completing the program–and most importantly, participants are already seeing tangible business results:
Congratulations to all 14 participating founders on their hard work in Google for Startups Sales Academy—we can’t wait to see what you do next!

Head to startup.google.com to learn more about Google for Startups resources and programs for African founders, such as Accelerator: Africa, Startup School, and the Google for Startups Black Founders Fund in Africa.





Posted by : Justin Nabozna, Google for Startups Global Partner Program Lead




 ==== 

Beta Channel Update for Chrome OS

The Beta channel has been updated to 94.0.4606.69 (Platform version: 14150.46.0) for most Chrome OS devices. This build contains a number of bug fixes, security updates and feature enhancements. 


If you find issues, please let us know by visiting our forum or filing a bug. Interested in switching channels? Find out how. You can submit feedback using 'Report an issue...' in the Chrome menu (3 vertical dots in the upper right corner of the browser).


Matt Nelson


Google Chrome OS