
New Maps updates and tips to navigate the holidays

ChromeOS M119 Stable
The Stable channel is being updated to OS version: 15633.44.0 Browser version: 119.0.6045.158 for most ChromeOS devices.
If you find new issues, please let us know one of the following ways
Interested in switching channels? Find out how.
Snapchat is a visual messaging app that enhances Snapchatters’ relationships with friends, family, and the world. It opens to the camera and offers millions of augmented reality and AI-powered Lenses for self expression, learning, and play. Ensuring Snapchatters can easily capture and share their lives with close friends and family is a priority for Snapchat, and they're always exploring new ways to improve the overall app experience.
As part of this, the Snapchat team added new camera features into the app using Android’s Camera2 Extensions API, which allows developers to access various capabilities that OEMs have implemented on various devices, like Night Mode and Bokeh. Thanks to Android’s intuitive API, the Snapchat team implemented new camera features 50% faster than before.
The Snapchat team wanted to optimize the application for the expanding selection of Android devices, knowing many OEMs differentiate their devices with their respective camera technologies. As Snapchat is a primarily visual app that works with a device’s camera, the team optimizes the app to take full advantage of each device’s unique hardware.
“We wanted to leverage each OEM’s software to enhance the Snapchat experience on Android,” said Ye Tian, a software engineer at Snapchat. “This would help the app achieve higher-quality Snaps that are comparable to what a device's native camera offers.”
What started as a goal to improve the app’s low-light capabilities led to much more. The Snapchat team worked on finding new ways to improve the app’s camera capabilities by implementing features like night mode, portrait mode, face retouch, tap-to-focus, zoom, and more.
“Our collaboration with Google Pixel paved the way for collaboration with other OEMs to implement night mode and super-night mode in their devices with very minimal code changes,” said Ye. “The Camera2 Extensions API is flexible and extensive. Snapchat can now use it to build full-fledged applications on demand without negatively impacting performance and stability.”
The implementation via the Camera2 Extension API made it easy for Snapchat developers to add more camera features into the app. And using the extensions made available with Android’s camera API, Snapchat integrated new camera features 50% faster when compared to the typical industry-standard approaches it used in the past.
The Snapchat team was happy to give its users a more cohesive experience using the Camera2 Extensions API. Thanks to the extensions provided in the API, developers easily improved the app’s camera on a range of manufacturer devices using the Android platform, and much faster than before.
“I enjoy the diversity of the Android platform and utilizing the unique advantages of each mobile phone manufacturers’ devices,” said Ye. “It helps us bring their cutting-edge innovations into the Snapchat app, allowing Snapchatters to better capture their life moments.”
Snapchat’s team looks forward to working with more OEMs to further improve the app’s processing capabilities across devices using the Camera2 Extensions API. They’re also looking forward to improving the app’s backward compatibility using the new API, which will allow even more users to benefit from the extensions.
“I would recommend using Camera2 Extension API. It provides extensive functionalities and stable performance to improve the velocity that developers can deliver features,” said Ye.
Learn how to increase your app’s camera capabilities with the Camera2 Extensions API.
Hi, everyone! We've just released Chrome 119 (119.0.6045.163) for Android: it'll become available on Google Play over the next few days.
This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.Last month we announced new changes launching in Google Ads API v15 to enable customers to pass end-user consent when uploading data. Today we are adding similar fields to Display & Video 360 API v2 and v3 that you can use when uploading Customer Match audience members.
You must start sending consent signals when uploading Customer Match audience members by March 2024 to adhere to the EU User Consent Policy and continue using European Economic Area (EEA) user data to populate Customer Match audiences.
What’s changing?
The Display & Video 360 API has added a Consent
object for uploading consent with your Customer Match data. The Consent
object specifies two distinct types of consent. For the EEA user data to be used in Customer Match user lists, both types of consent must be granted to indicate that you have received user consent.
What should I do?
Consent signals are set for all users added in a single firstAndThirdPartyAudiences.create
or firstAndThirdPartyAudiences.editCustomerMatchMembers
request. Use separate requests to upload users with different consent signals.
Make the following updates to requests creating and updating Customer Match audiences of the following audience types:
Audience Type | Relevant update |
CUSTOMER_MATCH_CONTACT_INFO
|
Set the consent field of the included ContactInfoList.
|
CUSTOMER_MATCH_DEVICE_ID
|
Set the consent field of the included MobileDeviceIdList.
|
We have updated the existing Customer Match feature guide with information on passing consent signals. Read our release notes for an itemized list of the changes.
Before using these new features, make sure to update your client library to the latest version.
Where can I get support?
If you have questions regarding these changes or need help with these new fields, please contact us using our support contact form.
The Extended Stable channel has been updated to 118.0.5993.144 for Windows and Mac which will roll out over the coming days/weeks.
A full list of changes in this build is available in the log. Interested in switching release channels? Find out how here. 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.
Hi everyone! We've just released Chrome Stable 119 (119.0.6045.169) for iOS; it'll become available on App Store in the next few hours.
This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.
Erhu Akpobaro
Google Chrome