Showing posts with label privacy. Show all posts

Android 11 final Beta update, official release coming soon!

Posted by Dave Burke, VP of Engineering

android

It’s already August and the official Android 11 release is coming very soon! As we put the finishing touches on the new platform, today we’re bringing you Beta 3, our last update in this year’s preview cycle. For developers, now is the time to make sure your apps are ready, before we bring the official release to consumers.

You can get Beta 3 today on Pixel 2, 3, 3a, and 4 devices (and coming soon, Pixel 4a!). Just enroll here for an over-the-air update. If you’re already enrolled, you’ll automatically get the update soon. As always, let us know your feedback, and thank you for all of the input you’ve provided so far.

Watch for more information on the official Android 11 release coming soon!

What’s in Beta 3?

Today’s update includes a release candidate build of Android 11 for Pixel devices and the Android Emulator. We reached platform stability at Beta 2, so all app-facing surfaces and behaviors are final, including SDK and NDK APIs, app-facing system behaviors, and restrictions on non-SDK interfaces. With these and the latest fixes and optimizations, Beta 3 gives you everything you need to complete your testing.

As we bring Android 11 to final form, we’re also taking this opportunity to update Android with the Exposure Notifications System in mind. Starting in Beta 3, users will be able to run Exposure Notification apps on Android 11 without needing to turn on the device location setting. This is an exception we’re making for the Exposure Notification System only, given that it has been designed in such a way that apps using it can’t infer device location through Bluetooth scanning. To protect user privacy, all other apps will still be prohibited from performing Bluetooth scanning unless the device location setting is on and the user has granted them location permission. You can read more in our Update on Exposure Notifications post.

Get your apps ready for Android 11!

With the official Android 11 release on the way, we’re asking all Android app and game developers to finish your compatibility testing and publish your updates soon. For SDK, library, tools, and game engine developers, it’s even more important to release a compatible version right away, since your downstream app and game developers may be blocked until they receive your updates.

how

As we covered in depth at Beta 2, here’s how to test for compatibility with Android 11.

For testing your current app, read behavior changes for all apps to identify areas where platform changes might affect your apps. Here are some of the top changes to watch for (these apply regardless of your app’s targetSdkVersion):

  • One-time permission - Users can now grant single-use permission to access location, device microphone and camera. Details here.
  • External storage access - Apps can no longer access other apps’ files in external storage. Details here.
  • Scudo hardened allocator - Scudo is now the heap memory allocator for native code in apps. Details here.
  • File descriptor sanitizer - Fdsan is now enabled by default to detect file descriptor handling issues for native code in apps. Details here.

Remember to test the libraries and SDKs in your app for compatibility. If you find an issue, try updating to the latest version of the SDK, or reach out to the developer for help.

For more information on compatibility testing and tools, check out the resources we shared for Android 11 Compatibility week and visit the Android 11 developer site for technical details.

Explore the new features and APIs

Android 11 has a ton of new features to build new experiences for users around people, controls, and privacy. When you’re ready to dive in, check out our #Android11 Beta post for a recap of all of the developer features, and you can also visit the Beta Launch page to see talks from the Android team on what’s new in their areas. For complete details on Android 11 features and APIs, visit the Android 11 developer site.

Also make sure to try the Android 11 features in Android Studio that can improve your productivity and workflow, like ADB incremental for faster installs of large APKs, and additional nullability annotations on platform APIs. You can give these a try by downloading the latest Android Studio Beta or Canary version. Instructions for configuring Android Studio for Android 11 are here.

How do I get Beta 3?

It’s easy! Just enroll here to get the Beta 3 update over-the-air on your Pixel 2, 3, 3a, or 4 device (and coming soon, Pixel 4a). If you're already enrolled, you'll receive the update soon and no action is needed on your part. Alternatively, you can give Android Flash Tool a try for easy on-demand updates, and if you’d rather flash manually, downloadable system images are also available. If you don't have a Pixel device, you can use the Android Emulator in Android Studio or try a GSI image to run Android 11 on supported Treble-compliant devices.

What’s next?

Stay tuned for the official Android 11 launch coming in the weeks ahead! In the meantime, we recommend finishing your testing and publishing your compatible updates as soon as possible. Feel free to share your feedback using our hotlists for filing platform issues (including privacy and behavior changes), app compatibility issues, and third-party SDK issues. You've given us great feedback so far -- thank you again!

A huge thank you to our developer community for your participation in our recent Android 11 AMA and Android Studio AMA on r/anddroiddev! It’s great to hear what’s important to you and we hope we were able to help!

Updates on our work to improve user privacy in digital advertising


Privacy is core to our work at Google, and to our vision for a thriving internet where people around the world can continue to access ad-supported content, while also feeling confident that their data is protected. But in order to get there, we must increase transparency into how digital advertising works, offer users additional controls, and ensure that people’s choices about the use of their data are respected—not worked around or ignored. 
Today we’re sharing updates on our work in these areas, including new tools that provide people more information about the ads they see. We’re also introducing new resources for marketers and publishers that offer guidance on how to navigate today’s privacy environment, along with real-world examples from brands and media companies who are delivering effective, privacy-forward ad experiences that use data responsibly.
Greater transparency, more control
For many years Google has offered a feature called Why this ad, where from an icon in a digital ad, users can get more information on some of the factors that were used to select the ad for them, or choose to stop seeing that ad. There are over 15 million user interactions per day with Why this ad as people seek to learn more about and control the ads they see, and we recently extended this feature to ads on connected TVs. 
Over the next few months, we’ll be making improvements to the experience with a new feature called About this ad, which will also show users the verified name of the advertiser behind each ad. About this ad will initially be available for display ads purchased through Google Ads and Display & Video 360, and we’ll bring it to other ad surfaces throughout 2021.
Our commitment to increase transparency and offer users more control goes beyond the ads Google shows. Due to the complexity of the digital ads ecosystem and the large number of entities involved, it’s typically not clear to users which companies are even involved in showing them an ad. To provide people with detailed information about all the ads they see on the web, we’re releasing a new tool called Ads Transparency Spotlight, now available to try out as an alpha extension from the Chrome Web Store. We’ll continue to improve this extension based on feedback from users, and over time we expect to offer additional disclosures about ads, as well as introduce controls. Our hope is that other technology providers will build similar transparency and control capabilities into the experiences they offer as well.  
Evolving the ad-supported internet
Chrome continues to explore more privacy-forward ways for the web browser to support digital ads with the Privacy Sandbox open standards initiative. As part of the Privacy Sandbox, several proposals have been published for new APIs that would solve for use cases like ad selection, conversion measurement, and fraud protection in a way that doesn’t reveal identifying information about individual users. One of the proposed APIs, for trust tokens that could combat ad fraud by distinguishing between bots and real users, is now available for testing by developers, and more will move to live testing soon.
Once these approaches have addressed the needs of users, publishers and advertisers, Chrome plans to phase out support for third-party cookies. These proposals are being actively discussed in forums like the W3C. Our ads team is actively contributing to this dialog—as we encourage any interested party to do—and we expect to incorporate the new solutions into our products in the years ahead.
We’re also exploring a range of other approaches to improve user privacy while ensuring publishers can earn what they need to fund great content and advertisers can reach the right people for their products. For example, we support the use of advertiser and publisher first-party data (based on direct interactions with customers they have relationships with) to deliver more relevant and helpful experiences—as long as users have transparency and control over the use of that data. What is not acceptable is the use of opaque or hidden techniques that transfer data about individual users and allow them to be tracked in a covert manner, such as fingerprinting. We believe that any attempts to track people or obtain information that could identify them, without their knowledge and permission, should be blocked. We’ll continue to take a strong position against these practices.
Much of the recent conversation about improving the privacy of digital ads has been focused on the web, but there are a range of environments in which people engage with digital ads. Our technical approach and the implementation details may vary based on the unique characteristics of each, but our vision to uplevel user privacy while preserving access to free content is consistent across web, mobile app, connected TV, digital audio -- and whatever the next area to emerge may be.
Guidance for advertisers and publishers
The future state of digital advertising promises new technologies, new standards, and better, more sustainable approaches, but it will take some time to get there. We recognize the unease that many in the industry feel during this period of transition. While there is certainly more change on the horizon, it’s critical that marketers and publishers do not wait to take action. 
To help you prepare, we’ve assembled a number of recommendations for marketers and publishers to consider today. From best practices for building direct relationships with your customers and managing data, to tips for evaluating your partner and vendor relationships, to actionable examples for using machine learning and the cloud, these playbooks offer practical guidance and numerous real-world examples of companies that are successfully navigating today’s changing privacy landscape. 
We’ll continue our work to move the digital ads industry towards a more privacy-forward future. In the meantime, make sure your organization is having an active discussion about privacy and that you are taking steps now to plan for what lies ahead.
Posted by Mike Schulman, VP, Ads Privacy and Safety
Subscribe to: Posts (Atom)