Dev Channel Update for Desktop

 The Dev channel has been updated to 103.0.5028.0 for Windows , Linux, and Mac.

A partial list of changes is available in the 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.

Srinivas Sista

Google Chrome

Chrome Beta for Android Update

Hi everyone! We've just released Chrome Beta 102 (102.0.5005.26) 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

This YouTuber wants to bring financial literacy to Africans

Nicolette Mashile wanted to find a more fulfilling career. So in 2016, she resigned from her job as a Client Service Director at a Johannesburg advertising agency. But quitting meant Nicolette was forced to stick to a stricter budget.

She began sharing her money-saving tips on YouTube and it wasn’t long before she noticed her advice resonated with African viewers. Eventually, this South African content creator built a significant following for her candid take on money management, and was invited to join the #YouTubeBlackVoices Creator Class of 2021. This in turn helped herFinancial Bunny YouTube channel garner almost 9 million views.

“I was very frank about money management, how to effectively budget and how to plan your spending. When I saw my YouTube following growing, I knew this personal finance advice was making a real impact and I committed to improving financial literacy in South Africa,” Nicolette says.

This meant finding creative ways to make financial literacy more inclusive and accessible while also removing the stigma attached to discussing personal finance. Nicolette spun her YouTube success into two books — one for adults titled “What’s Your Move,” and another for children, “Coco the Money Bunny.”

“When I created the books, I had to develop a new website so it was important to identify our different customer types and implement search engine optimization. I needed to do research to understand the target customers and develop the website to meet their needs and Google Ads was a promotional channel I experimented with,” Nicolette added.

But it was the launch of her Save or Spend board game and subsequent app that sparked her shift towards technology.

“I’d successfully leveraged digital media to share financial content, so naturally it made sense to use the power of tech to design an interactive app that could simplify money management in a fun and engaging way,” she says.

Using gamification helped to take away the seriousness around money while also addressing the lack of financial education in South Africa. In a digital era where most Africans own a smartphone rather than a laptop, Nicolette knew a free app would be an accessible tool to teach people about money. Her app has proven popular due in large part to the massive following she has built online since launching her YouTube channel back in 2017.

Nicolette’s also grown her business to include consultancy and coaching, and she relies a lot on Google Meets for some of her sessions.

“My consultancy work with brands and corporate individuals means I use video calling quite often and for this I use Google Meets. I do one-on-one coaching with multiple clients per month and it’s super simple to just send a link and jump on a call because people can log in from anywhere,” she says.

Ultimately, Nicolette hopes to continue empowering her followers by arming them with the tools and skills they need to better manage their money. “I want to keep encouraging South Africans to have the difficult discussions people often avoid around personal finance.”

Fifty-eight percent of Africa’s entrepreneurs are women. That’s why we’re empowering them with the platform and tools to grow their businesses. #LookMeUp is a call for all to #BreakTheBias. Find out more here.

How can App Engine users take advantage of Cloud Functions?

Posted by Wesley Chun (@wescpy), Developer Advocate, Google Cloud

Introduction

Recently, we discussed containerizing App Engine apps for Cloud Run, with or without Docker. But what about Cloud Functions… can App Engine users take advantage of that platform somehow? Back in the day, App Engine was always the right decision, because it was the only option. With Cloud Functions and Cloud Run joining in the serverless product suite, that's no longer the case.

Back when App Engine was the only choice, it was selected to host small, single-function apps. Yes, when it was the only option. Other developers have created huge monolithic apps for App Engine as well… because it was also the only option. Fast forward to today where code follows more service-oriented or event-driven architectures. Small apps can be moved to Cloud Functions to simplify the code and deployments while large apps could be split into smaller components, each running on Cloud Functions.

Refactoring App Engine apps for Cloud Functions

Small, single-function apps can be seen as a microservice, an API endpoint "that does something," or serve some utility likely called as a result of some event in a larger multi-tiered application, say to update a database row or send a customer email message. App Engine apps require some kind web framework and routing mechanism while Cloud Function equivalents can be freed from much of those requirements. Refactoring these types of App Engine apps for Cloud Functions will like require less overhead, helps ease maintenance, and allow for common components to be shared across applications.

Large, monolithic applications are often made up of multiple pieces of functionality bundled together in one big package, such as requisitioning a new piece of equipment, opening a customer order, authenticating users, processing payments, performing administrative tasks, and so on. By breaking this monolith up into multiple microservices into individual functions, each component can then be reused in other apps, maintenance is eased because software bugs will identify code closer to their root origins, and developers won't step on each others' toes.

Migration to Cloud Functions

In this latest episode of Serverless Migration Station, a Serverless Expeditions mini-series focused on modernizing serverless apps, we take a closer look at this product crossover, covering how to migrate App Engine code to Cloud Functions. There are several steps you need to take to prepare your code for Cloud Functions:

  • Divest from legacy App Engine "bundled services," e.g., Datastore, Taskqueue, Memcache, Blobstore, etc.
  • Cloud Functions supports modern runtimes; upgrade to Python 3, Java 11, or PHP 7
  • If your app is a monolith, break it up into multiple independent functions. (You can also keep a monolith together and containerize it for Cloud Run as an alternative.)
  • Make appropriate application updates to support Cloud Functions

    The first three bullets are outside the scope of this video and its codelab, so we'll focus on the last one. The changes needed for your app include the following:

    1. Remove unneeded and/or unsupported configuration
    2. Remove use of the web framework and supporting routing code
    3. For each of your functions, assign an appropriate name and install the request object it will receive when it is called.

    Regarding the last point, note that you can have multiple "endpoints" coming into a single function which processes the request path, calling other functions to handle those routes. If you have many functions in your app, separate functions for every endpoint becomes unwieldy; if large enough, your app may be more suited for Cloud Run. The sample app in this video and corresponding code sample only has one function, so having a single endpoint for that function works perfectly fine here.

    This migration series focuses on our earliest users, starting with Python 2. Regarding the first point, the app.yaml file is deleted. Next, almost all Flask resources are removed except for the template renderer (the app still needs to output the same HTML as the original App Engine app). All app routes are removed, and there's no instantiation of the Flask app object. Finally for the last step, the main function is renamed more appropriately to visitme() along with a request object parameter.

    This "migration module" starts with the (Python 3 version of the) Module 2 sample app, applies the steps above, and arrives at the migrated Module 11 app. Implementing those required changes is illustrated by this code "diff:"

    Migration of sample app to Cloud Functions

    Next steps

    If you're interested in trying this migration on your own, feel free to try the corresponding codelab which leads you step-by-step through this exercise and use the video for additional guidance.

    All migration modules, their videos (when published), codelab tutorials, START and FINISH code, etc., can be found in the migration repo. We hope to also one day cover other legacy runtimes like Java 8 as well as content for the next-generation Cloud Functions service, so stay tuned. If you're curious whether it's possible to write apps that can run on App Engine, Cloud Functions, or Cloud Run with no code changes at all, the answer is yes. Hope this content is useful for your consideration when modernizing your own serverless applications!

The first developer preview of Privacy Sandbox on Android

Posted by Fred Chung, Android Developer Relations

Blue graphic with privacy icons such as an eye, a lock, and cursor 

We recently announced the Privacy Sandbox on Android to enable new advertising solutions that improve user privacy, and provide developers and businesses with the tools to succeed on mobile. Since the announcement, we've heard from developers across the ecosystem on our initial design proposals. Your feedback is critical to ensure we build solutions that work for everyone, so please continue to share it through the Android developer site.

Today, we're releasing the first developer preview for the Privacy Sandbox on Android, which provides an early look at the SDK Runtime and Topics API. You'll be able to do preliminary testing of these new technologies and evaluate how you might adopt them for your solutions. This is a preview, so some features may not be implemented just yet, and functionality is subject to change. See the release notes for more details on what's included in the release.


What’s in the Developer Preview?

The Privacy Sandbox Developer Preview provides additional platform APIs and services on top of the Android 13 Developer Beta release, including an SDK, system images, emulator, and developer documentation. Specifically, you'll have access to the following:

  • Android SDK and 64-bit Android Emulator system images that include the Privacy Sandbox APIs. See the setup guide.
  • Device system images for Pixel 6 Pro, Pixel 6, Pixel 5a (5G), Pixel 5, Pixel 4, and Pixel 4a. This preview release is for developers only and not intended for daily or consumer use, so we're making it available by manual download only.
  • Developer guides for the SDK Runtime and Topics API.
  • Sample code that demonstrates the implementation of runtime-enabled SDKs and usage of the Topics API, available on GitHub.
  • Privacy Sandbox API reference.

Things you can try

When your development environment is set up, consider taking the following actions:

  • Familiarize yourselves with the technical proposals on the SDK Runtime, Topics, Attribution Reporting, and FLEDGE on Android.
  • Topics API: Invoke the API and retrieve test values, representing a user's coarse-grained interests. See the documentation for detail.
  • SDK Runtime: Build and install a runtime-enabled SDK on a test device or emulator. Create a test app to load the SDK in the runtime and request the SDK to remotely render a WebView-based ad in the app. See the documentation for detail.
  • Review and run the sample apps.
  • For details on capabilities and known limitations in this Developer Preview release, check out the release notes.

Over the coming months, we'll be releasing updates to the Developer Preview including early looks at the Attribution Reporting and FLEDGE APIs. For more information, please visit the Privacy Sandbox developer site. You can also share your feedback or questions, review progress updates so far, and sign up to receive email updates.

Happy testing!

The Package Analysis Project: Scalable detection of malicious open source packages

Despite open source software’s essential role in all software built today, it’s far too easy for bad actors to circulate malicious packages that attack the systems and users running that software. Unlike mobile app stores that can scan for and reject malicious contributions, package repositories have limited resources to review the thousands of daily updates and must maintain an open model where anyone can freely contribute. As a result, malicious packages like ua-parser-js, and node-ipc are regularly uploaded to popular repositories despite their best efforts, with sometimes devastating consequences for users.

Google, a member of the Open Source Security Foundation (OpenSSF), is proud to support the OpenSSF’s Package Analysis project, which is a welcome step toward helping secure the open source packages we all depend on. The Package Analysis program performs dynamic analysis of all packages uploaded to popular open source repositories and catalogs the results in a BigQuery table. By detecting malicious activities and alerting consumers to suspicious behavior before they select packages, this program contributes to a more secure software supply chain and greater trust in open source software. The program also gives insight into the types of malicious packages that are most common at any given time, which can guide decisions about how to better protect the ecosystem.

To better understand how the Package Analysis program is contributing to supply chain security, we analyzed the nearly 200 malicious packages it captured over a one-month period. Here’s what we discovered: 

Results

All signals collected are published in our BigQuery table. Using simple queries on this table, we found around 200 meaningful results from the packages uploaded to NPM and PyPI in a period of just over a month. Here are some notable examples, with more available in the repository.

PyPI: discordcmd
This Python package will attack the desktop client for Discord on Windows. It was found by spotting the unusual requests to raw.githubusercontent.com, Discord API, and ipinfo.io.

First, it downloaded a backdoor from GitHub and installed it into the Discord electron client.

Next, it looked through various local databases for the user's Discord token.


Finally, it grabbed the data associated with the token from the Discord API and exfiltrated it back to a Discord server controlled by the attacker.

NPM: @roku-web-core/ajax

During install, this NPM package exfiltrates details of the machine it is running on and then opens a reverse shell, allowing the remote execution of commands.
This package was discovered from its requests to an attacker-controlled address.

Dependency Confusion / Typosquatting

The vast majority of the malicious packages we detected are dependency confusion and typosquatting attacks.


The packages we found usually contain a simple script that runs during an install and calls home with a few details about the host. These packages are most likely the work of security researchers looking for bug bounties, since most are not exfiltrating meaningful data except the name of the machine or a username, and they make no attempt to disguise their behavior.


These dependency confusion attacks were discovered through the domains they used, such as burpcollaborator.net, pipedream.com, interact.sh, which are commonly used for reporting back attacks. The same domains appear across unrelated packages and have no apparent connection to the packages themselves. Many packages also used unusual version numbers that were high (e.g. v5.0.0, v99.10.9) for a package with no previous versions.Conclusions

The short time frame and low sophistication needed for finding the results above underscore the challenge facing open source package repositories. While many of the results above were likely the work of security researchers, any one of these packages could have done far more to hurt the unfortunate victims who installed them.

These results show the clear need for more investment in vetting packages being published in order to keep users safe. This is a growing space, and having an open standard for reporting would help centralize analysis results and offer consumers a trusted place to assess the packages they’re considering using. Creating an open standard should also foster healthy competition, promote integration, and raise the overall security of open source packages.
 
Over time we hope that the Package Analysis program will offer comprehensive knowledge about the behavior and capabilities of packages across open source software, and help guide the future efforts needed to make the ecosystem more secure for everyone. To get involved, please check out the GitHub Project and Milestones for opportunities to contribute.

Women Techmakers expands online safety education

Online violence against women goes beyond the internet. It impacts society and the economy at large. It leads to damaging economic repercussions, due to increased medical costs and lost income for victims. It impacts the offline world, with seven percent of women changing jobs due to online violence, and one in ten experiencing physical harm due to online threats, according to Google-supported research conducted by the Economist Intelligence Unit in 2020.

That’s why the Women Techmakers program, which provides visibility, community and resources for women in technology, supports online safety education for women and allies. Google community manager Merve Isler, who lives in Turkey and leads Women Techmakers efforts in Turkey, Central Asia and the Caucasus region, organized the first-ever women’s online safety hackathon in Turkey in 2020, which expanded to a full week of trainings and ideathons in 2021. Google community manager and Women Techmakers manager Hufsa Manawar brought online safety training to Pakistan in early 2022.

Now, Women Techmakers is providing a more structured way for women around the world to learn about online safety, in the form of a free online learning module, launched in April 2022, in honor of International Women’s Day. To create this module, I worked with my co-host Alana Fromm from Jigsaw and our teams to create a series of videos covering different topics related to women’s online safety. Jigsaw is a unit within Google that explores threats to open society and builds technological solutions.

In the online training, we begin by defining online violence and walking through the ways negative actors threaten women online, which include misinformation and defamation, cyberharassment and hate speech. Regardless of the tactic, the goal remains the same: to threaten and harass women into silence. We break down the groups of people involved in online harassment and the importance of surrounding oneself with allies.

In one of the videos in the series, Women Techmakers Ambassador Esrae Abdelnaby Hassan shares her story of online abuse. She was exploring learning cybersecurity when a mentor she trusted gave her USB drives with courses and reading material that were infected with viruses and allowed him to take control of her computer and record videos. Then, he blackmailed her, using the videos he’d taken as threats. She felt afraid and isolated, and relied on her family for support as she addressed the harassment.

The learning module provides two codelabs, one on steps you can take to protect yourself online, and one on Perspective API, a free, open-source product built by Jigsaw and the Counter Abuse security team at Google. The first codelab provides practical guidance, and the second codelab walks viewers through the process of installing Perspective API, which uses machine learning to identify toxic comments.

We look forward to seeing the impact of our new, easy-to-access online training, as well as what our ambassadors are able to accomplish offline as the year progresses.

Coming together to protect the global internet

The global internet began with an incredible promise: a shared resource that everyone could access wherever they lived. Over the last few years, this ideal has been strained to the breaking point as governments around the world have adopted conflicting regulations that are fragmenting the internet to the detriment of people everywhere.

That’s why it’s great to see countries coming together today to launch the Declaration for the Future of the Internet (DFI). Through this effort, allies across the public and private sectors will work together to protect the importance of the global web, including by opposing shutdowns and other “efforts to splinter the global Internet.”

Digital fragmentation impacts everyone using the internet. As conflicting regulations proliferate, people’s access to content, privacy protections, and freedom to transact and communicate increasingly vary depending on where they are located. Digital fragmentation has become a significant barrier to international trade, with a particularly pernicious effect on small businesses, which lack the resources to navigate an array of conflicting rules. And it discriminates against smaller, developing countries, as new products become harder to launch and scale on a fragmented Internet to all markets.

The DFI provides a path to address the most urgent threats to the global internet. In particular, we’re seeing a number of governments take actions to crack down on the free flow of information and ideas, increase government surveillance, and restrict access to cross-border internet services under the banner of “cyber-sovereignty.”

The DFI joins the EU-US Trade & Tech Council and the Indo-Pacific Economic Framework as important fora where like-minded partners can join together to address cross-border challenges. We hope this work will be grounded in a few key principles:

  • First, governments should strive to agree on common standards to guide the development of new rules for digital technologies, so that consumers have consistent protections across borders and access to digital tools.
  • Second, governments should strive to increase interoperability between national digital rules, as we’ve seen with the US-EU Data Privacy Framework.
  • Third, governments should commit to intergovernmental regulatory dialogue to ensure that new rules strengthen shared values.
  • And fourth, governments should abide by core open trade principles like non-discriminatory approaches to regulation that don’t single out foreign companies.

The private sector also plays an important role in maintaining the global internet. That’s especially true in times of crisis, as security teams work to disrupt disinformation campaigns, cyber attacks and other online threats. Since Russia’s invasion in Ukraine, our teams have been working around the clock to support people in Ukraine through our products, defend against cybersecurity threats, and surface high-quality, reliable information. We are committed to partnering with governments and civil society through the Declaration to disrupt disinformation campaigns and foreign malign activity, while ensuring people around the world are able to access trustworthy information.

Ultimately, the cross-border availability of secure technologies and digital services – coupled with forward-looking decisions by governments – can protect access to information everywhere and ensure that the enormous benefits resulting from the global internet are not lost. We stand ready to support the DFI’s mission to promote an open, secure, and reliable internet for all.

Reforming the patent system to support American innovation

Over the years, Google has worked to ensure that the United States patent system continued to spur new inventions and technologies. A healthy patent system incentivizes and rewards the most original and creative inventors — while helping others build on existing ideas and avoiding frivolous litigation. Supporting that balanced approach, we were one of the first companies to pledge not to sue any user, distributor, or developer of open-source software on specified patents, unless first attacked. We helped found the License on Transfer (LOT) Network, which shields its members from being sued over patents that other members have sold to patent trolls. And we worked in collaboration with others to create a repository of hard-to-find “prior art” documents to improve the patenting process, resulting in higher quality patents.

We have also invested heavily in patenting our engineers’ inventions in advanced technologies. Our tens of thousands of engineers have authored over 42,000 home-grown patents and we have licensed hundreds of thousands more at fair value. We are proud of our patented innovations like the ability to predict traffic or extend battery life. And we have sold hundreds of patents to smaller companies interested in bolstering their own portfolios.

But we are concerned that America’s patent system is increasingly failing to promote the cause of innovation and progress. The quality of patents issued in the U.S is declining. And, after a few years where earlier reforms reduced abusive patent litigation, it’s back with force, with 46% more lawsuits in 2021 than in 2018. Patent trolls and opportunistic companies have begun to weaponize patents against their rivals, hindering both competition and innovation, and ultimately harming the quality of new products. America’s prized “culture of innovation” is being undermined by a “culture of litigation.”

Reversing the rising tide of wasteful patent litigation

Aggressive litigants waste valuable court resources unsuccessfully trying to stretch patents beyond recognition. And prolific patent trolls wage litigation shakedown campaigns with low-quality patents that are later found to be invalid, wasting time and resources that could have been spent on developing new products.

Google is a resourceful company with a strong record of fighting overreaching patent claims, and we can defend our users and products. But many smaller companies, especially those producing nascent technologies, cannot afford the risk and expense of these lawsuits, which raise costs for consumers and stifle companies’ ability to bring products to market. That is why we are calling for more support for the United States Patent and Trademark Office (PTO), reforms to how the judicial system handles patent claims, and Congressional changes to address patent abuse.

Investing in the Patent Office

Each year, the PTO approves more than half of the more than 600,000 patent applications it receives, working to balance incentives for investment and freedom to innovate. Evaluating those applications is a monumental task and in recent years the agency has not had the tools it needs to do its job right. Technology can help, and the PTO is working on AI solutions to streamline the process. But its hard-working employees remain under-resourced to keep up with advancing technology. This results in invalid patents getting issued to inventors, which undermines their ability to protect technology confidently. Others face the cost and hassle of defending infringement claims against patents that should never have been granted in the first place. This isn’t fair for anyone except patent trolls.

Ending forum shopping

There are 677 federal district court judgeships in the United States. But many companies suing over patent claims are gaming the system. This forum shopping has gotten so out of hand that almost 25% of all US patent litigation is now being filed in a single courthouse. After a bipartisan request for action, Chief Justice John Roberts has committed to investigate the issue and push to restore the integrity of the judicial process.

Restoring Inter Partes Review

On top of all this, changes to PTO rules have weakened Inter Partes Review (IPR), the program that Congress created to help companies cost-effectively invalidate low-quality patents. Congress carefully constructed the IPR program to provide expert review of the small subset of patents with the greatest impact on our economy. But new PTO policies make it harder to use IPRs to invalidate patents in a cost-effective and streamlined way.

Preserving America’s culture of innovation

A series of steps would improve the current system, benefiting both innovation and consumers:

  • At the United States Patent and Trademark Office, a new director is now at the helm, with a clear mandate to improve patent quality as set out in the Commerce Department’s Strategic Plan. To do so, the Office should work to ensure that the agency’s process for reviewing an application for a patent is robust, and that patents that shouldn’t have been granted can be promptly, efficiently, and effectively challenged. Of course, that will require giving the PTO the resources it needs. The PTO is funded by fees paid by patent applicants, and we support increasing fees for the largest patent filers, including Google. With the confirmation of PTO Director Kathi Vidal, this important work can finally begin.
  • In the judiciary, the Supreme Court’s year-end report on the federal judiciary made the issue of forum shopping one of three topics of focus for 2022. As the review requested by the Chief Justice moves forward, we hope it urgently addresses the judicial imbalances caused by abusive forum shopping.
  • Finally, before Congress, there is pending, bipartisan legislation that would help reduce abusive patent litigation. We are supportive of the goals of this bill, which would restore access to the Inter Partes Review program and increase transparency and accountability. It makes clear that the PTO is the most effective forum for reviewing patent validity, giving the Office the opportunity to double-check its own work in an efficient, expert, and cost-effective way. We and a broad cross-section of supporters rallied behind this program back in 2011 when it was enacted as part of the America Invents Act with resounding bipartisan support, and it’s time to live up to its original purpose.

With changes like these, we are optimistic that the patent system can get back to what it is intended to do: preserve the U.S. culture of innovation, advance the development of new technology, and reward entrepreneurs who are building new products that benefit American consumers and people around the world.

Girlguiding and Google: technology is for everyone

Technology has always been a huge part of my life. Growing up in the nineties and early noughties, I can’t remember a time without it. From chunky flip phones and CDs, to newer, sleeker gadgets with all sorts of capabilities, technology has changed rapidly and remarkably in my lifetime alone.

But, despite growing up around tech, I — like lots of my female peers — never really felt I could be involved in creating it. This needs to change. Technology can be made by anyone, and is for everyone. We need to make sure that girls and young women have the opportunity to pursue an interest in STEM subjects.

That’s why, as a Ranger and Young Leader within Girlguiding, I’m really excited about Girlguiding’s newly expanded programme with Google which will give nearly 400,000 Rainbows, Brownies, Guides and Rangers more opportunities to learn digital skills for their future.

Girls feel STEM is not for them

To encourage more girls and young women to pursue STEM subjects, we need to change attitudes from a very young age. Girlguiding’s Girls’ Attitudes Survey, found in 2021 that 52% of girls aged 11-21 saw STEM subjects as “for boys”. Girls of this age are at a stage where they’re making choices about their future, but sadly, preconceived perceptions are impacting their aspirations.

A third (34%) aged 7 to 21 feel there’s a lack of women role models in STEM. One in five (19%) aged 7 to 10 say girls who are interested in STEM subjects are teased. 27% of girls aged 11 to 21 believe teachers and career advisors often encourage girls to do different subjects to boys.

These numbers really highlight the need for groups like Girlguiding to work with organizations like Google to change this and enable more young people to feel empowered to pursue their interests.

Digital discovery badges

Google and Girlguiding first launched the Google Digital Adventure for Brownies and Digital design badge for Rangers in 2018. More than 15,000 girls have already taken part.

Now, we’re expanding our partnership to give more girls and young women opportunities to learn about concepts like coding and algorithms, with new activities co-created by Google’s women engineers.

The new activities include Happy appy for Rainbows to learn about app designs; Brownie bots to teach Brownies how to write code and fix bugs; Chattermatter to teach Guides about chatbots, and Build-a-phone, which aims to teach Rangers the basic principles of phone design.

The new activities will form part of Girlguiding’s national programme within the Skills for my Future theme. These span all four Girlguiding sections (age groups) and have been created to be completed offline to ensure they are accessible to all girls.

An exciting future for all girls

Our goal — to make sure the next generation of girls and young women are encouraged to pursue STEM subjects — may not happen overnight. But thanks to the Girlguiding and Google partnership, nearly 400,000 girls like me in the UK will get new opportunities to learn the essential skills they need to break through stereotypes and become tech pioneers.

In years to come, I hope to see the Rainbows or Brownies of today on the front cover of a newspaper showing off their incredible discoveries and inventions. Alongside Google, Girlguiding is working to help build a future where more girls and young women feel empowered to help change the world!

Want to find out more? Read all about the new Google and Girlguiding partnership at www.girlguiding.org.uk.