Grow your games business with new ads solutions

Whether it’s to join the latest multiplayer craze or dive back into an old favorite, user interest in gaming worldwide continues to rise as people spend more time at home. In fact, our data shows that global searches for “best online games” between February and April were up over 100 percent compared to the same time last year. 

Mobile game developers have a huge opportunity to connect with these eager players around the globe. This week at Think Games in China, we’re announcing new ways for developers to engage with the right players and maximize revenue so your team can spend more time creating awesome gaming experiences.  

Reach more of the right players for your game

In today’s crowded gaming landscape, it’s not easy to build a community and retain players over time. App campaigns for engagement were built to help you get players who’ve previously installed your game to return, with custom messages across Search, YouTube and over 1 million apps in our network. 

Available globally in September, App campaigns for engagement will soon also run in Google Play and support audiences from Google Analytics for Firebase. We’re also updating our audience management features to make it easier for you to connect with the right player segments. 

Ads Keynote _ Think Games at ChinaJoy 2020-02.jpg

App campaigns for engagement will soon be able to serve ads in the Play Store

FunPlus, the developers behind the mobile strategy game King of Avalon, wanted to find ways to also get current players to come back during a mega update event. It used App campaigns for engagement to create custom messages for previous player groups who had stopped playing. This resulted in 34 percent more high-value players returning to play, as compared to other strategies it used.

E02557939 Google GMP Think Games at ChinaJoy Update 1 King of Avalon Jul20 v01 (1).jpg

To get started with App campaigns for engagement, make sure you set up deep linking and app conversion tracking, and use a supported measurement solution like Google Analytics for Firebase or one of our App Attribution Partners.  

Here are a few more features designed to help you reach players across the lifecycle of your game:  

  • App campaigns for pre-registration: Get a head start in building an excited community for your game before it launches. Learn more.
  • Maximize conversions bidding for App campaigns for installs: Drive as many installs as possible within a set budget to reach your campaign goals. Learn more.
  • Target Return on Ad Spend (tROAS) open beta for App campaigns for installs: Adjust your bids dynamically based on the value each user is likely to bring for your game. Available later this year to all advertisers bidding on Google Analytics for Firebase events. Learn more. 
  • Creative simplification: Simplify your creative development process by creating image ads only in 1.91:1, 1:1, and 4:5 aspect ratios. You can also crop existing image assets to these aspect ratios with our new cropping tool. Learn more.

Maximize your ad revenue

To help you get the most value from your ads, Open Bidding will be available as a beta to all AdMob developers this fall. Today, many developers rely solely on waterfall mediation, a tried-and-true way to monetize with multiple advertising sources that can be hard to set up and manage at scale. Waterfall mediation calls ad networks one at a time until one of them returns an ad. Though effective, you could be losing out on additional revenue since networks are prioritized based on historical CPMs, rather than real-time pricing.

As Google’s in-app bidding solution, Open Bidding puts participating networks in a fair real-time auction to compete for your impressions, so the winner is always the highest paying network. This means you’ll get the highest revenue available for every impression. With Open Bidding, you can find the most popular demand sources to compete for your impressions in real time. Open Bidding makes earning more even easier by eliminating the need to manually set CPMs and reducing the number of SDKs your teams need to integrate and manage. 

10954_Google_OpenBidding_960x540.gif

CookApps used Open Bidding in order to grow revenue for its match-three puzzle game Candy Blast. By switching to Open Bidding, CookApps optimized revenue across ad networks and saw a 26 percent increase in both total ad revenue and CPMs, compared to their previous waterfall mediation setup. Open Bidding also enabled teams to save time from managing multiple networks, allowing it to focus on other priorities to expand its business. 

E02557939 Google GMP Think Games at ChinaJoy Update 1 Cook Apps Jul20 v01 (1).jpg

Along with Open Bidding, we’re announcing several other solutions to simplify your setup so you can earn even more from your apps:

  • Impression-level LTV pingback: Get real-time estimates of impression values to help measure lifetime value of players across all revenue sources (iOS, Android, Unity).

  • Rewarded interstitials: Increase engagement with rewarded ads by proactively showing players in-game offers in exchange for watching a video during gameplay breaks.

  • App open beta: See up to twice as much user engagement with the improved user experience of app open ads, which now offer standardized publisher branding and simplified user tap targets.Learn more.

  • AdMob plug-in for Unity software: Create and edit ads easily in the Unity interface, letting you quickly implement ads into your Unity game with just a single line of code. 

To hear more about how these solutions can help you build your community and grow your business, watch the Ads Announcements session and tune in to the full Think Gameslive stream.  

Making privacy personal with Files by Google

In many places around the world, sharing a personal device with spouses, siblings or children is often a cultural expectation, especially for women. Sharing a device can be beneficial, but it comes with the risk that others might access your personal files.


As part of Google’s research, we hear the perspectives of people like Shaina—a woman in Bangladesh whose children use her phone after school, both to learn and to play. Shaina worries that her important files could be accidentally shared or deleted. For Rashid, a father in India, the lack of privacy means he can’t keep his identity documents on his phone, even if he needs them for job applications. 


Building privacy features that make sense for different needs is a top priority for us as we continue to work towards a more inclusive internet. To keep personal content more safe, we're launching Safe Folder, a new feature in Files by Google.

How Safe Folder works


Safe Folder is a secure, 4-digit PIN-encrypted folder that protects your important documents, images, videos and audio files from being opened or accessed by others. The folder is securely locked as soon as you switch away from the Files app, so none of its contents can be accessed when the app is in the background. As a security assurance, it will ask for your PIN again on reentry.  Even people that don't share devices can benefit from keeping the most important files safe.
File Safe Folder gif

Managing files for 150 million people


We launched the Files app in 2017 to help people free up space, manage content and share files. We wanted to help people who live in countries such as India, Nigeria and Brazil and often run out of space on a daily basis. Now, more than 150 million people around the world regularly use Files each month, reducing the stress of managing content on their phones.


Files Safe Folder gif 2

And for the things you no longer need on your phone? Files can continue to help you with that. Since launch, the app has:


  • Deleted over 1 trillion files of digital clutter, which would take over 30,000 years if you were to manually remove a duplicate, old meme or junk file every second.

  • Saved 400+ petabytes of space on people’s phones—around 1,400 years of nonstop HD video recording.

  • Freed about 12GB of space every second, equivalent to 5,000 photos per second, allowing you to save more photos that mean a lot to you.  

The Safe Folder feature will start rolling out in beta for Files by Google today and we’ll gradually expand its availability to more people over the following weeks. You can get the app at g.co/getfiles to keep your content safe, free up space and make your phone feel like new.

Support for Southeast Asian startups tackling big challenges

Southeast Asia’s startups have helped build a thriving internet economy. Now, they have an equally important role to play in the recovery from the COVID-19 pandemic—and in tackling some of the biggest challenges Southeast Asia faces around education, health, e-commerce, logistics and financial technology.


In June, we launched Google for Startups Accelerator: Southeast Asia, a three-month online program to support startups working on social, economic and health problems across the region. We received more than 600 applications, and today we’re announcing the 15 startups chosen for the first cohort.
SEA Startup Accelerator cohort logos

Over the next few months, these startups will receive mentorship on both technical and business challenges. We’ll also connect them to teams from Google and the wider technology industry, and provide workshops focused on designing products, customer service and leadership development for founders.


Here’s the full list of startups. We can’t wait to help them move their ideas forward as they make a difference for Southeast Asians over the next decade and beyond.


  • Advance (Philippines) is a credit platform that provides short-term salary advances for Filipino employees.

  • DeafTawk (Pakistan) has created a digital sign language interpretation service platform that breaks down communication barriers.

  • GIZTIX (Thailand) is an integrated logistics platform that helps customers grow their businesses and reduce operating costs.

  • Hacktiv8 (Indonesia) helps train beginner developers, supports them in finding jobs and provides a new, fairer type of student loan.  

  • Kata.ai (Indonesia) has developed a conversational artificial intelligence platform that enables more natural conversations between businesses and their customers.

  • MHub (Malaysia) is an end-to-end property transaction platform which makes the process of buying a home easier by linking property developers, real-estate agents and potential customers.  

  • Riliv (Indonesia) has created an online counseling and meditation app to help people with their mental health.  

  • Rumarocket (Philippines) has developed an AI tool that helps companies make hiring decisions using behavioral science.

  • Sehat Kahani (Pakistan) is working on providing access to affordable, technology-enabled healthcare via a network of qualified home-based women doctors.

  • SenzeHub (Singapore) offers a wearable, AI-powered device that determines a patient's location and does vitals reading and crisis detection. 

  • Shoplinks (Singapore) provides consumer-goods clients with tools to digitize their customer engagements and promotions.

  • Smartfuture (Singapore) is a telemedicine platform and self-monitoring diagnostic kiosk that allows users to check key health vitals

  • Thuocsi.vn (Vietnam) is an online platform to buy medicine, first aid and dispensary items

  • TopCV (Vietnam) is a recruitment platform that better connects recruiters and candidates.

  • Walee (Pakistan) is a trading app to connect businesses looking to sell items online with social influencers who want to collaborate with them.

August update to Display & Video 360 API v1

Today we’re releasing an update to the Display & Video 360 API v1 which includes the following features:


More detailed information about this update can be found on the Display & Video 360 API release notes page.

Before using these new features, make sure to update your client to the latest version. For more information on how to use some of these new features, you can read our new User Management guide and Auditing Account Limits page.

If you run into issues or need help with these new features, please contact us using our support contact form.

August update to Display & Video 360 API v1

Today we’re releasing an update to the Display & Video 360 API v1 which includes the following features:


More detailed information about this update can be found on the Display & Video 360 API release notes page.

Before using these new features, make sure to update your client to the latest version. For more information on how to use some of these new features, you can read our new User Management guide and Auditing Account Limits page.

If you run into issues or need help with these new features, please contact us using our support contact form.

Dev Channel Update for Desktop

The Dev channel has been updated to 86.0.4221.3/.4 for Windows & Mac, 86.0.4221.3 for Linux platforms.
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.
Google Chrome
Prudhvikumar Bommana

Delivering security and privacy for Exchange on Android

For many Android users, Microsoft Exchange is the backend for their company email. Until recently, many email applications on Android used Device Admin capabilities to enforce the necessary security requirements on users’ devices, whether they were issued by their company or personally owned.

These APIs, which we began deprecating in Android 9 Pie, gave IT control over core security features such as device passcode requirements and remote data wipe. While this gives IT admins controls to promote data protection on the devices when using Exchange email clients, it also adds unnecessary complexity.

We've worked closely with Microsoft to create a new set of APIs that give email developers tools to secure their apps while adhering to the high standards we've set in Android for user privacy.

Google and Microsoft work together for user privacy

We teamed up with Microsoft to build a new way to offer the security that IT needs when using Microsoft Exchange, while offering the privacy employees have come to expect on personal Android devices.

IT admins have the option to require a user to follow a specified level of password complexity (options are for high, medium or low) to use their Exchange email app. If they don’t follow the set guidelines, they won’t be able to sync and access their corporate email. If IT needs to restrict or remove access on the device, no personal information, such as photos or downloads, will be removed. 

Combined with other Android technologies like the SafetyNet Attestation API, Android hardware-backed brute force protections and Google Play Protect, IT professionals can feel confident their data is protected by enterprise-grade security while giving their employees greater autonomy over their device. 

Bringing these improvements to more users

To make sure as many users as possible can benefit from this change, the Android team has developed a backwards-compatible implementation of this approach in Google Mobile Services. Email app developers can migrate away from Device Admin on any version of Android they support.

Gmail will showcase this new functionality later this month. As Android app developers update apps to meet the official Device Admin deprecation requirements in Android 10 later this year, look for your favorite email client to take advantage of this functionality soon.

For companies whose needs evolve and would benefit from even greater management capabilities, we invite them to learn more at android.com/enterprise.

How insights from people around the world make Google Search better

Every Google search you do is one of billions we receive that day. In less than half a second, our systems sort through hundreds of billions of web pages to try and find the most relevant and helpful results available.


Because the web and people’s information needs keep changing, we make a lot of improvements to our search algorithms to keep up. Thousands per year, in fact. And we’re always working on new ways to make our results more helpful whether it’s a new feature, or bringing new language understanding capabilities to Search.


The improvements we make go through an evaluation process designed so that people around the world continue to find Google useful for whatever they’re looking for. Here are some ways that insights and feedback from people around the world help make Search better.


Our research team at work

Changes that we make to Search are aimed at making it easier for people to find useful information, but depending on their interests, what language they speak, and where they are in the world, different people have different information needs. It’s our mission to make information universally accessible and useful, and we are committed to serving all of our users in pursuit of that goal.


This is why we have a research team whose job it is to talk to people all around the world to understand how Search can be more useful. We invite people to give us feedback on different iterations of our projects and we do field research to understand how people in different communities access information online.


For example, we’ve learned over the years about the unique needs and technical limitations that people in emerging markets have when accessing information online. So we developed Google Go, a lightweight search app that works well with less powerful phones and less reliable connections. On Google Go, we’ve also introduced uniquely helpful features, including one that lets you listen to web pages out loud, which is particularly useful for people learning a new language or who may be less comfortable with reading long text. Features like these would not be possible without insights from the people who will ultimately use them.


Search quality raters

A key part of our evaluation process is getting feedback from everyday users about whether our ranking systems and proposed improvements are working well. But what do we mean by “working well”? We publish publicly available rater guidelines that describe in great detail how our systems intend to surface great content. These guidelines are more than 160 pages long, but if we have to boil it down to just a phrase, we like to say that Search is designed to return relevant results from the most reliable sources available.


Our systems use signals from the web itself—like where words in your search appear on web pages, or how pages link to one another on the web—to understand what information is related to your query and whether it’s information that people tend to trust. But notions of relevance and trustworthiness are ultimately human judgments, so to measure whether our systems are in fact understanding these correctly, we need to gather insights from people.


To do this, we have a group of more than 10,000 people all over the world we call “search quality raters.” Raters help us measure how people are likely to experience our results. They provide ratings based on our guidelines and represent real users and their likely information needs, using their best judgment to represent their locale. These people study and are tested on our rater guidelines before they can begin to provide ratings.


How rating works

Here’s how a rater task works: we generate a sample of queries (say, a few hundred). A group of raters will be assigned this set of queries, and they’re shown two versions of results pages for those searches. One set of results is from the current version of Google, and the other set is from an improvement we’re considering.


Raters review every page listed in the results set and evaluate that page against the query, based on our rater guidelines. They evaluate whether those pages meet the information needs based on their understanding of what that query was seeking, and they consider things like how authoritative and trustworthy that source seems to be on the topic in the query. To evaluate things like expertise, authoritativeness, and trustworthiness—sometimes referred to as “E-A-T”—raters are asked to do reputational research on the sources.


Here’s what that looks like in practice: imagine the sample query is “carrot cake recipe.” The results set may include articles from recipe sites, food magazines, food brands and perhaps blogs. To determine if a webpage meets their information needs, a rater might consider how easy the cooking instructions are to understand, how helpful the recipe is in terms of visual instructions and imagery, and whether there are other useful features on the site, like a shopping list creator or calculator for recipe doubling. 


To understand if the author has subject matter expertise, a rater would do some online research to see if the author has cooking credentials, has been profiled or referenced on other food websites, or has produced other great content that has garnered positive reviews or ratings on recipe sites. Basically, they do some digging to answer questions like: is this page trustworthy, and does it come from a site or author with a good reputation?  


Ratings are not used directly for search ranking

Once raters have done this research, they then provide a quality rating for each page. It’s important to note that this rating does not directly impact how this page or site ranks in Search. Nobody is deciding that any given source is “authoritative” or “trustworthy.” In particular, pages are not assigned ratings as a way to determine how well to rank them. Indeed, that would be an impossible task and a poor signal for us to use. With hundreds of billions of pages that are constantly changing, there’s no way humans could evaluate every page on a recurring basis.


Instead, ratings are a data point that, when taken in aggregate, helps us measure how well our systems are working to deliver great content that’s aligned with how people—across the country and around the world—evaluate information.


Last year alone, we did more than 383,605 search quality tests and 62,937 side-by-side experiments with our search quality raters to measure the quality of our results and help us make more than 3,600 improvements to our search algorithms. 


In-product experiments

Our research and rater feedback isn’t the only feedback we use when making improvements. We also need to understand how a new feature will work when it’s actually available in Search and people are using it as they would in real life. To make sure we’re able to get these insights, we test how people interact with new features through live experiments.


They’re called “live” experiments because they’re actually available to a small proportion of randomly selected people using the current version of Search. To test a change, we will launch a feature to a small percentage of all queries we get, and we look at a number of different metrics to measure the impact.


Did people click or tap on the new feature? Did most people just scroll past it? Did it make the page load slower? These insights can help us understand quite a bit about whether a new feature or change is helpful and if people will actually use it.


In 2019, we ran more than 17,000 live traffic experiments to test out new features and improvements to Search. If you compare that with how many launches actually happened (around 3600, remember?), you can see that only the best and most useful improvements make it into Search.


Always improving

While our search results will never be perfect, these research and evaluation processes have proven to be very effective over the past two decades. They allow us to make frequent improvements and ensure that the changes we make represent the needs of people around the world coming to Search for information.


Source: Search


Automatic Deployment of Hugo Sites on Firebase Hosting and Drafts on Cloud Run

Posted by James Ward, Developer Advocate

Recently I completed the migration of my blog from Wordpress to Hugo and I wanted to take advantage of it now being a static site by hosting it on a Content Delivery Network (CDN). With Hugo the source content is plain files instead of rows in a database. In the case of my blog those files are in git on GitHub. But when the source files change, the site needs to be regenerated and redeployed to the CDN. Also, sometimes it is nice to have drafts available for review. I setup a continuous delivery pipeline which deploys changes to my prod site on Firebase Hosting and drafts on Cloud Run, using Cloud Build. Read on for instructions for how to set all this up.

Step 1a) Setup A New Hugo Project

If you do not have an existing Hugo project you can create a GitHub copy (i.e. fork) of my Hugo starter repo:

Step 1b) Setup Existing Hugo Project

If you have an existing Hugo project you'll need to add some files to it:

.firebaserc

{
"projects": {
"production": "hello-hugo"
}
}

cloudbuild-draft.yaml

steps:
- name: 'gcr.io/cloud-builders/git'
entrypoint: '/bin/sh'
args:
- '-c'
- |
# Get the theme git submodule
THEME_URL=$(git config -f .gitmodules --get-regexp '^submodule\..*\.url$' | awk '{ print $2 }')
THEME_DIR=$(git config -f .gitmodules --get-regexp '^submodule\..*\.path$' | awk '{ print $2 }')
rm -rf themes
git clone $$THEME_URL $$THEME_DIR

- name: 'gcr.io/cloud-builders/docker'
entrypoint: '/bin/sh'
args:
- '-c'
- |
docker build -t gcr.io/$PROJECT_ID/$REPO_NAME-$BRANCH_NAME:$COMMIT_SHA -f - . << EOF
FROM klakegg/hugo:latest
WORKDIR /workspace
COPY . /workspace
ENTRYPOINT hugo -D -p \$$PORT --bind \$$HUGO_BIND --renderToDisk --disableLiveReload --watch=false serve
EOF
docker push gcr.io/$PROJECT_ID/$REPO_NAME-$BRANCH_NAME:$COMMIT_SHA

- name: 'gcr.io/cloud-builders/gcloud'
args:
- run
- deploy
- --image=gcr.io/$PROJECT_ID/$REPO_NAME-$BRANCH_NAME:$COMMIT_SHA
- --platform=managed
- --project=$PROJECT_ID
- --region=us-central1
- --memory=512Mi
- --allow-unauthenticated
- $REPO_NAME-$BRANCH_NAME

cloudbuild.yaml

steps:
- name: 'gcr.io/cloud-builders/git'
entrypoint: '/bin/sh'
args:
- '-c'
- |
# Get the theme git submodule
THEME_URL=$(git config -f .gitmodules --get-regexp '^submodule\..*\.url$' | awk '{ print $2 }')
THEME_DIR=$(git config -f .gitmodules --get-regexp '^submodule\..*\.path$' | awk '{ print $2 }')
rm -rf themes
git clone $$THEME_URL $$THEME_DIR

- name: 'gcr.io/cloud-builders/curl'
entrypoint: '/bin/sh'
args:
- '-c'
- |
curl -sL https://github.com/gohugoio/hugo/releases/download/v0.69.2/hugo_0.69.2_Linux-64bit.tar.gz | tar -zxv
./hugo

- name: 'gcr.io/cloud-builders/wget'
entrypoint: '/bin/sh'
args:
- '-c'
- |
# Get firebase CLI
wget -O firebase https://firebase.tools/bin/linux/latest
chmod +x firebase
# Deploy site
./firebase deploy --project=$PROJECT_ID --only=hosting

firebase.json

{
"hosting": {
"public": "public"
}
}


Step 2) Setup Cloud Build Triggers

In the Google Cloud Build console, connect to your newly forked repo: Select the newly forked repo: Create the default push trigger: Edit the new trigger: Set the trigger to only fire on changes to the ^master$ branch: Create a new trigger: Give it a name like drafts-trigger, specify the branch selector as .* (i.e. any branch), and the build configuration file type to "Cloud Build configuration file" with a value of cloudbuild-draft.yaml Setup permissions for the Cloud Build process to manage Cloud Run and Firebase Hosting by visiting the IAM management page, locate the member with the name ending with @cloudbuild.gserviceaccount.com, and select the "pencil" / edit button: Add a role for "Cloud Run Admin" and another for "Firebase Hosting Admin": Your default "prod" trigger isn't read to test yet, but you can test the drafts on Cloud Run by going back to the Cloud Build Triggers page, and clicking the "Run Trigger" button on the "drafts-trigger" line. Check the build logs by finding the build in the Cloud Build History. Once the build completes visit the Cloud Run console to find your newly created service which hosts the drafts version of your new blog. Note that the service name includes the branch so that you can see drafts from different branches.

Step 3) Setup Firebase Hosting

To setup your production / CDN'd site, login to the firebase console and select your project:

Now you'll need your project id, which can be found in the URL on the Firebase Project Overview page. The URL for my project is:

console.firebase.google.com/project/jw-demo/overview

Which means my project id is: jw-demo

Now copy your project id go into your GitHub fork, select the .firebaserc file and click the "pencil" / edit button:

Replace the hello-hugo string with your project id and commit the changes. This commit will trigger two new builds, one for the production site and one for the drafts site on Cloud Run. You can check the status of those builds on the Cloud Build History page. Once the default trigger (the one for Firebase hosting) finishes, check out your Hugo site running on Firebase Hosting by navigating to (replacing YOUR_PROJECT_ID with the project id you used above): https://YOUR_PROJECT_ID.web.app/

Your prod and drafts sites are now automatically deploying on new commits!

Step 4) (Optional) Change Hugo Theme

There are many themes for Hugo and they are easy to change. Typically themes are pulled into Hugo sites using git submodules. To change the theme, edit your .gitmodules file and set the subdirectories and url. As an example, here is the content when using the mainroad theme:

[submodule "themes/mainroad"]
path = themes/mainroad
url = https://github.com/vimux/mainroad.git

You will also need to change the theme value in your config.toml file to match the directory name in the themes directory. For example:

theme = "mainroad"

Note: At the time of writing this, Cloud Build does not clone git submodules so the cloudbuild.yaml does the cloning instead.

Step 5) (Optional) Setup Local Editing

To setup local editing you will first need to clone your fork. You can do this with the GitHub desktop app. Or from the command line:

git clone --recurse-submodules https://github.com/USER/REPO.git

Once you have the files locally, install Hugo, and from inside the repo's directory, run:

hugo -D serve

This will serve the drafts in the site. You can check out the site at: localhost:1313

Committing non-draft changes to master and pushing those changes to GitHub will kick off the build which will deploy them on your prod site. Committing draft to any branch will kick off the build which will deploy them on a Cloud Run site.

Hopefully that all helps you with hosting your Hugo sites! Let me know if you run into any problems.

Instantly share files with people around you with Nearby Share

The Android community has long asked for a way to quickly share content with each other from their devices. So after years of development, Android is launching Nearby Share, a platform to enable reliable and easy sharing across thousands of Android phone models and billions of people.

Nearby Share is rolling out to Android 6.0+ phones today, making it easier to instantly share files, links, pictures and more with people around you, all while protecting your privacy. 


Easily share content both online and offline

When you just want to quickly share something with a friend or someone nearby, it can be a hassle to open your messages, find a contact and then find the file you’d like to attach. Nearby Share allows you to cut down on that time with simple taps and see a list of devices in your proximity with which you can share content. Once you select the receiver, they will be notified with the option to either accept or decline the file. Nearby Share then automatically chooses the best protocol for fast and easy sharing using Bluetooth, Bluetooth Low Energy, WebRTC or peer-to-peer WiFi — allowing you to share even when you’re fully offline.


ASL_Nearby_Share_Creative_V07.gif

Safely share and receive files with those around you

Nearby Share was built with privacy at its core, so you can share and receive files with peace of mind. Now you don’t have to worry about exchanging contact information, because Nearby Share allows you to both send and receive files anonymously. It also allows you to adjust your privacy settings from your phone’s Quick Settings at any time. You can be “hidden,” visible to “some contacts” or visible to “all contacts,” so you never receive files that you didn’t ask for.

Nearby_Pixel_Shell_Settings-03.png

Works smoothly with Chromebooks

In the coming months, Nearby Share will work with Chromebooks so you can swiftly share files between an Android phone and a Chromebook, and vice versa. Chromebooks already have features that make them work especially well with Android, like Instant Tethering, and Nearby Share will make Android and Chromebook work even better together. 

Nearby_CHROME_PIXEL-02.png

Select Google Pixel and Samsung devices will be the first smartphones to receive Nearby Share starting today. We will continue to work with our partners to bring Nearby Share to more smartphones in the Android ecosystem over the next few weeks. Visit our support page to learn more about how to enable Nearby Share and adjust your visibility settings.