Monthly Archives: May 2018

New insights in Google Docs Activity dashboard

We’re introducing new features to provide more insight and help you collaborate through Activity dashboard in Google Docs, Sheets, and Slides. This will help make the data in Activity dashboard:

  • More actionable. Users can quickly email file collaborators. 
  • More useful. Users can see viewing patterns over time. 


Email collaborators through Activity dashboard 

In just a few clicks, users can pick recipients, customize, and send a follow-up email with the link to the file. Users can:

  • Select who to email. There are shortcuts for collaborators who have viewed the file or have not viewed the file, or you can pick recipients manually with checkboxes (see image below for example). 
  • Customize an email. Users can write a message to chosen recipients. 
  • Send the email. 

See our Help Center for detailed instructions on how to send emails through Activity dashboard




See viewing patterns over time 

A popular request from our users is to have more insight into patterns around viewing data on files. So we’re adding a chart showing how many viewers have visited the file over time. You can adjust the date range, and hover over specific data points for more details.



Use our Help Center to find out more about how to understand the data in Activity dashboard.

Launch Details
Release track:
Launching to Rapid Release, with Scheduled Release coming in two weeks

Editions:
Available on G Suite Business, Enterprise, Education, and Nonprofit editions

Rollout pace:
Gradual rollout (up to 15 days for feature visibility)

Impact:
All end users

Action:
Change management suggested/FYI

More Information





Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

Chrome for Android Update

Good news, everyone!  Chrome 67 (67.0.3396.68) for Android has been released and will be available on Google Play over the course of the next few weeks. Thanks for choosing Chrome! This release includes stability and performance improvements.

A list of the changes in this build is available in the Git log.

If you find a new issue, please let us know by filing a bug. More information about Chrome for Android is available on the Chrome site.

Estelle Yomba
Google Chrome

Leveling the STEM playing field for girls, one robot at a time

I was introduced to competitive student robotics seven years ago, when my fifth-grade son developed an interest with his friends. My daughter followed in those footsteps, and through their experiences, I saw how differently STEM is presented to and approached by boys and girls. I wanted to help level the playing field by making it easier for girls to develop a passion for STEM. I’d already built a space in my garage to coach kids about robotics, and I decided it was time to expand the effort so that more girls could get involved.


Last year, along with a scrappy group of Googlers and high school students, I hosted a workshop with the VEX Girl Powered initiative and eventually partnered with the Girl Scouts of Northern California. We developed an after-school program where middle and high school age girls work on their robots with Google volunteers and prepare for several competitions. We just wrapped up our first year of the program, with 68 girls participating across 11 teams. Three of the middle school teams—{Access Denied}, Lightning Bots and RoboPros2.0n—qualified for state championships!


Here’s what a few of Google’s volunteers—Rebecca Shapley, a business analyst for Google’s Developer Platform team; Nupur Garg, a software engineer on TensorFlow; and Dave Wu, Silicon Architecture EPM at Nest—had to say about their experience working with the girls:


Tell us about the project your team worked on.

Rebecca: The girls built a robot to lift and move cones within a 10’ by 10’ game-zone. The game is designed to reward both simple robots and additional complexity. A simple robot might lift a big cone and move it to a scoring zone, but a more complex robot will put a smaller cone on the big cone, and drive over a pipe to put it in a higher scoring zone. An ace robot will put the smaller cones in large stacks, and be able to score points autonomously, without a human driver, in the first few seconds of the game.


What’s been the most rewarding part of working with the girls?

Nupur: None of the girls on my team had previously done anything related to robotics, so the most rewarding part of working with the girls was seeing their growth. They went from being new to everything to taking ownership of what they wanted to accomplish each session. Over the last month of the program, they decided to build a more competitive robot that tackled elements of the game they had not previously attempted. There is nothing that replaces the feeling of seeing students grow and knowing you played a part in that.


Dave: It was rewarding to start from scratch and then design, redesign, refine and work as a team to compete and win various competitions.  


Rebecca: I didn’t have a background in robotics, so I really enjoyed learning vicariously through the girls! It also threw into relief for me those other skills that support successful technical development, like scientific problem solving, designing, work planning, organizing group efforts and decisions, and systematic thinking. Even though I didn’t know much about robots, I could contribute by modeling these skills, and know that this could translate to the rest of their lives too.

Is there a standout moment from your experience as a coach?

Rebecca: About six weeks in, all of us coaching the team could tell that a shift had happened. Their sense of ownership over the robot blossomed. As adults we stepped back and focused on getting the right balance in supporting their success while letting them lead.


Dave: Watching the girls work hard in the last few sessions leading to the first competition and maturing together as a team during the competition.


Nupur: When I asked the girls at their last competition if they wanted to do this again next year, they all eagerly told me they wanted to stay with the same team and work on a more competitive robot next year. They were confident that they could build something completely on their own that could compete with the more experienced teams in the high school division.


What can be done to get more girls involved in robotics?

Rebecca: More opportunities and more skilled people mentoring! The all-girls teams were great—the ratio of girls represented in mixed teams was substantially lower. Successful teams need time, practice space, robot pieces, mentoring, parent support, and design support.


Dave: Provide spaces and materials (like what Google did) so that more girls can get involved, and expose more parents to the program.


Nupur: It’s important to create a positive environment where the girls can learn and where failure is encouraged.


This summer, we hope to bring even greater awareness to STEM with our Girl Powered workshop in August. If you’re interested in signing up for future robotics workshops, you can indicate interest via this form.

Dev Channel Update for Chrome OS

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

If you find new 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). 


Bernie Thompson
Google Chrome

Introducing the Data Studio Community Connector Codelab

Cross-posted from the Google Developer blog 
Posted by Minhaz Kazi, Developer Advocate, Google Data Studio


Data Studio is Google’s free next gen business intelligence and data visualization platform. Community Connectors for Data Studio let you build connectors to any internet-accessible data source using Google Apps Script. You can build Community Connectors for commercial, enterprise, and personal use. Learn how to build Community Connectors using the Data Studio Community Connector Codelab.

Use the Community Connector Codelab 

The Community Connector Codelab explains how Community Connectors work and provides a step by step tutorial for creating your first Community Connector. You can get started if you have a basic understanding of Javascript and web APIs. You should be able to build your first connector in 30 mins using the Codelab.

If you have previously imported data into Google Sheets using Apps Script, you can use this Codelab to get familiar with the Community Connectors and quickly port your code to fetch your data directly into Data Studio.

Why create your own Community Connector 

Community Connectors can help you to quickly deliver an end-to-end visualization solution that is user-friendly and delivers high user value with low development efforts. Community Connectors can help you build a reporting solution for personal, public, enterprise, or commercial data, and also do explanatory visualizations.

  • If you provide a web based service to customers, you can create template dashboards or even let your users create their own visualization based on the users’ data from your service. 
  • Within an enterprise, you can create serverless and highly scalable reporting solutions where you have complete control over your data and sharing features. 
  • You can create an aggregate view of all your metrics across different commercial platforms and service providers while providing drill down capabilities. 
  • You can create connectors to public and open datasets. Sharing these connectors will enable other users to quickly gain access to these datasets and dive into analysis directly without writing any code. 

By building a Community Connector, you can go from scratch to a push button customized dashboard solution for your service in a matter of hours.

The following dashboard uses Community Connectors to fetch data from Stack Overflow, GitHub, and Twitter. Try using the date filter to view changes across all sources:


This dashboard uses the following Community Connectors:
You can build your own connector to any preferred service and publish it in the Community Connector gallery. The Community Connector gallery now has over 90 Partner Connectors connecting to more than 450 data sources.

Once you have completed the Codelab, view the Community Connector documentation and sample code on the Data Studio open source repository to build your own connector.

Insider Attack Resistance

Posted by Shawn Willden, Staff Software Engineer

Our smart devices, such as mobile phones and tablets, contain a wealth of personal information that needs to be kept safe. Google is constantly trying to find new and better ways to protect that valuable information on Android devices. From partnering with external researchers to find and fix vulnerabilities, to adding new features to the Android platform, we work to make each release and new device safer than the last. This post talks about Google's strategy for making the encryption on Google Pixel 2 devices resistant to various levels of attack—from platform, to hardware, all the way to the people who create the signing keys for Pixel devices.

We encrypt all user data on Google Pixel devices and protect the encryption keys in secure hardware. The secure hardware runs highly secure firmware that is responsible for checking the user's password. If the password is entered incorrectly, the firmware refuses to decrypt the device. This firmware also limits the rate at which passwords can be checked, making it harder for attackers to use a brute force attack.

To prevent attackers from replacing our firmware with a malicious version, we apply digital signatures. There are two ways for an attacker to defeat the signature checks and install a malicious replacement for firmware: find and exploit vulnerabilities in the signature-checking process or gain access to the signing key and get their malicious version signed so the device will accept it as a legitimate update. The signature-checking software is tiny, isolated, and vetted with extreme thoroughness. Defeating it is hard. The signing keys, however, must exist somewhere, and there must be people who have access to them.

In the past, device makers have focused on safeguarding these keys by storing the keys in secure locations and severely restricting the number of people who have access to them. That's good, but it leaves those people open to attack by coercion or social engineering. That's risky for the employees personally, and we believe it creates too much risk for user data.

To mitigate these risks, Google Pixel 2 devices implement insider attack resistance in the tamper-resistant hardware security module that guards the encryption keys for user data. This helps prevent an attacker who manages to produce properly signed malicious firmware from installing it on the security module in a lost or stolen device without the user's cooperation. Specifically, it is not possible to upgrade the firmware that checks the user's password unless you present the correct user password. There is a way to "force" an upgrade, for example when a returned device is refurbished for resale, but forcing it wipes the secrets used to decrypt the user's data, effectively destroying it.

The Android security team believes that insider attack resistance is an important element of a complete strategy for protecting user data. The Google Pixel 2 demonstrated that it's possible to protect users even against the most highly-privileged insiders. We recommend that all mobile device makers do the same. For help, device makers working to implement insider attack resistance can reach out to the Android security team through their Google contact.

Acknowledgements: This post was developed in joint collaboration with Paul Crowley, Senior Software Engineer

Insider Attack Resistance

Posted by Shawn Willden, Staff Software Engineer

Our smart devices, such as mobile phones and tablets, contain a wealth of personal information that needs to be kept safe. Google is constantly trying to find new and better ways to protect that valuable information on Android devices. From partnering with external researchers to find and fix vulnerabilities, to adding new features to the Android platform, we work to make each release and new device safer than the last. This post talks about Google's strategy for making the encryption on Google Pixel 2 devices resistant to various levels of attack—from platform, to hardware, all the way to the people who create the signing keys for Pixel devices.

We encrypt all user data on Google Pixel devices and protect the encryption keys in secure hardware. The secure hardware runs highly secure firmware that is responsible for checking the user's password. If the password is entered incorrectly, the firmware refuses to decrypt the device. This firmware also limits the rate at which passwords can be checked, making it harder for attackers to use a brute force attack.

To prevent attackers from replacing our firmware with a malicious version, we apply digital signatures. There are two ways for an attacker to defeat the signature checks and install a malicious replacement for firmware: find and exploit vulnerabilities in the signature-checking process or gain access to the signing key and get their malicious version signed so the device will accept it as a legitimate update. The signature-checking software is tiny, isolated, and vetted with extreme thoroughness. Defeating it is hard. The signing keys, however, must exist somewhere, and there must be people who have access to them.

In the past, device makers have focused on safeguarding these keys by storing the keys in secure locations and severely restricting the number of people who have access to them. That's good, but it leaves those people open to attack by coercion or social engineering. That's risky for the employees personally, and we believe it creates too much risk for user data.

To mitigate these risks, Google Pixel 2 devices implement insider attack resistance in the tamper-resistant hardware security module that guards the encryption keys for user data. This helps prevent an attacker who manages to produce properly signed malicious firmware from installing it on the security module in a lost or stolen device without the user's cooperation. Specifically, it is not possible to upgrade the firmware that checks the user's password unless you present the correct user password. There is a way to "force" an upgrade, for example when a returned device is refurbished for resale, but forcing it wipes the secrets used to decrypt the user's data, effectively destroying it.

The Android security team believes that insider attack resistance is an important element of a complete strategy for protecting user data. The Google Pixel 2 demonstrated that it's possible to protect users even against the most highly-privileged insiders. We recommend that all mobile device makers do the same. For help, device makers working to implement insider attack resistance can reach out to the Android security team through their Google contact.

Acknowledgements: This post was developed in joint collaboration with Paul Crowley, Senior Software Engineer

Expand your mind with Talks at Google on mental health and wellbeing

Editor’s Note:Talks at Google is our regular speaker series that brings interesting speakers and brilliant minds from all industries and backgrounds to Google campuses all around the world. Each month, we select a few favorite talks from that month, or about a particular topic.

Mental health touches all of us, whether as personally lived experience, or through a family member, friend, or community member. The National Institute of Mental Health estimates that nearly one in five adults in the U.S. lives with a mental illness. As Mental Health Awareness Month in May comes to a close, we’re looking back on talks at Google about how to talk about mental health, face life’s toughest challenges, and creatively foster your own wellbeing.

Thubten Chodron is a Tibetan Buddhist nun and co-author of a book with the Dalai Lama. She visited Google to share insights on finding internal contentment through connection with others. (Google taught her a little something too—specifically, the definition of an “algorithm.”)

Thubten Chodron: "Creating Habits for Happiness" | Talks at Google

How is balancing eggs a mindfulness activity? Licensed clinical psychologist and author Dr. Janna Koretz worked with teacher and illustrator Annie Hirschhorn on “Heroic Henrietta,” a book designed to help parents and kids navigate anxiety. Koretz specializes in the diagnosis of learning disabilities, ADHD, and psychological disorders for children and adolescents. Interventions that manage anxiety are similar across ages, making Henrietta's story of coping with anxiety relevant for many.

Dr. Janna Koretz and Annie Hirschhorn: "Heroic Henrietta" | Talks at Google

Assistant professor and author Kristin Neff explores the differences between self-compassion and self-esteem in her talk. She breaks self-compassion down into three components: kindness toward oneself, recognition of common humanity, and mindfulness, and guides the audience through a “self-compassion break” that you can try out at home.

Kristin Neff: "The Science of Self-Compassion" | Talks at Google

“Who here has experienced anxiety?” In the audience, many avert their eyes … an “avoidance behavior,” says Irish author and medical doctor Harry Barry. Barry’s work dissects how anxiety, fear and phobias are expressed through the body. In exploring the role of the brain and body when dealing with panic, he recommends lifestyle changes and cognitive behavioral therapy techniques to cope with symptoms and improve wellbeing.

Dr. Harry Barry: "Flagging Anxiety & Panic" | Talks at Google

Innovate with Google at the 2018 China-US Young Maker Competition!

Posted by Aimin Zhu, University Relations Manager, Google China

Following the announcement of the 2018 China-U.S. Young Maker Competition, we are very excited that there are already over 1000 participants with over a month left before the final submission deadline! Project submissions are open to all makers, developers, and students age 18-40 in the United States. Check out the projects others are developing on the project submissions page.

Participants may choose to develop their projects using any platform. Makers and students in the US are encouraged to consider the many Google technologies and platforms available to build innovative solutions:

The project submission deadline is June 22, so there is still plenty of time to join the competition! If you have additional questions about the competition or the project submission process, please visit the contest FAQ.

The top 10 projects selected by the judges will win an all-expenses-paid trip to Beijing, China, to join the finals with Chinese makers on August 13-17. We look forward to meeting you at the final event!

For more details, please see US divitional contest landing page hosted by Hackster.io.