 Chrome 86 introduced changes to the Trusted Web Activity Quality criteria. The Play Billing API will soon be available to PWAs via Trusted Web Activity. And PWAs can now be uploaded to the Play Store on Chrome OS. I'm André Banda. And I'm Adriana Jara, and let us show you how to prepare your app and take advantage of the new features. We recently launched Bubble Wrap, a common line too that helps web developers to use their PWA in an Android app. We continue to improve the tool. And we're happy to say that external dependencies are now downloaded automatically when running the tool for the first time, no more messing around with downloading files, unzipping, or typing in paths. The app creation flow was also improved with more helpful description of the input fields and better validation. A frequent request from developers of game and media applications was to be able to start apps in immersive mode and locked into a specific orientation from a home screen. And the Bubble Wrap now supports exactly that. It is possible to choose the startup modes when initializing the application. Users expect applications installed under devices to have consistent behavior, regardless of technology. When inside the Trusted Web Activity, the geolocation permission can now be delegated to the operating system. When enabled, users will see the same dialogues as apps built with Kotlin or Java, and find controls to manage the permission in familiar places. One of the advantages of using Trusted Web Activity is that the output binaries are small. Bubble Wrap has been optimized and now generates binaries that are 800K smaller. That's less than half the size generated by previous versions. Bubble Wrap is also now capable of generating app bundle files, which is a different format to package an app when publishing to the Play Store. Developers should now prefer this format, as it will be required by the Play Store, starting on the second half of 2021. As a developer creating an Android app, you will need to update your app on the Play Store from time to time. Reasons might include new Trusted Web Activity features or changes to the Android ecosystem. To update an application, starting by ensuring you have the latest version of Bubble Wrap, then run Bubble Wrap Update to apply the latest application template to an existing project. Finally, run Bubble Wrap Build to generate the application binary. The quality criteria has changed on Chrome 86. And users in the web app are now delegated to the Android app. This ensures that developers are either handling those users properly in the web app or that the application crashes in a way that is consistent to order applications on the device, regardless of technology. It's implemented for three different situations. First, when validation of the relationship between the web app and the Android app fails. Second, when the app fails to handle the offline scenario and the Chrome dinosaur would be displayed. Finally, when opening pages that cause the server to return a 404 or a 500-EHR, the best way to handle those EHRs is to prevent them from happening in the first place. And you can use a service worker to do just that. This snippet shows a Workbox plugin that handled those scenarios. Learn more about creating custom strategies for Workbox on the exciting Workbox talk by Jeff Posnick. Finally, for more information on the quality criteria changes, check out the linked blog post. We received feedback from developers worried about devices where Chrome is not installed or is not the user's preferred browser. With Samsung Internet adding support for trusted web activity from version 13 and above, we are happy to say that most browsers on Android now support trusted web activity. Besides being a requirement when selling digital goods, Google Play Billing enables developers to remove friction from purchase flows. And we are happy to announce that, starting on Chrome 88, developers beginning with trusted web activity will be able to combine the payment request API and the Digital Goods API to implement purchase flows via Google Play Billing. My colleague Adriana will tell us more about how to use the Digital Goods API on the web app and configure it on the Play Store. Over to you, Adriana. Thank you, André. As André mentioned, the Digital Goods API gives you access to tools in the Play Store that make managing digital goods purchases easier for you and for your users. To use the Play Billing payment flow, you'll need to configure your catalog on the Play Store, as well as connect the Play Store as a payment method from your PWA. To walk you through the process, let's say I have an app to create the perfect digital banana bread. I have created the trusted web activity and added the listing to the Play Store. Let's start by configuring our product catalog. In the Play Console, on the left side menu, find the Monetize section and then go to Products. There, we can create in-app products or subscriptions. For our example, in-app products would be things like bananas or nuts for the bread. Here, you can see a list of existing products and use the Create Product button to add a new one. We'll need a product ID, a name, a description, as well as a price. It's important to create meaningful and easy to remember product IDs. You'll need them later, and IDs cannot be changed once created. For the product to be available for purchase, after creating it, you will also need to activate it. We could also offer special features like secret ingredients via a subscription. Subscriptions are also set up in the Products section. You'll need to add product ID, name, description, price, and a billing period. You can also list the subscription benefits, and if you want, you can add a trial period, an introductory price, and a grace period for your subscription. You could also insert and manage products using the Play Developers API. Check out the link on the screen for more information. When the user is ready to purchase the product, you'll need to use the Web Payments API. When creating the payment request, you'll need to specify the Play Store information in the Supported Methods field and provide the product ID in the Data.SQU field. Once the transaction is complete, the response from the payment request submission will provide purchase details. That includes a purchase token. To complete the transaction, you must acknowledge the purchase with a snippet like this. The acknowledgement lets the Play Store know you received a successful purchase and have given the user the corresponding entitlement. Note that the purchase token received from the Play Store is not automatically associated with the user. The developer must handle given entitlement for the purchases and saving the token linked with the user to their backend. This token will be used to verify if the purchase is still valid or if the subscription is still active and give the user the appropriate entitlement. I just described only the basic flow. Look out for a companion blog post with more details about Play Billing for Web. It will include details about managing your subscriptions, using real-time developer notifications, and more information about Google Play Developer's API. On other news, from Chrome 85, Trusted Web Activities can also be installed on Chromebooks. For the best experience on Chrome OS, your Trusted Web activity should not include any native Android code. If you want to restrict your app to be installable only on Chromebooks, you can manually add this flag to your Android manifest. And if you use Bubble Wrap, we have an option that will add the configuration for you. One last reminder, every app that is listed on the Play Store must comply with the Google Play policy. Check out this video for more information. Capabilities like handling full screen and delegating geolocation, as well as new features in Bubble Wrap, make integrating your PWA with the Play Store better than ever. And Play Billing gives users a familiar and easy to use checkout flow. We hope you give them a try and send our way your comments or questions. Thank you.