 Welcome to Chrome Dev Summit 2020. I'm Dion. And I'm Ben. We work on the Chrome team and we're your hosts for this year's keynote. It sure has been a memorable year. And we're as excited as we think you are that it's nearly over. CDS has always been about bringing the Chrome team together with the community so we can learn from each other. We're really sad that we're unable to gather in person but we're doing our best to replicate this experience online. Both with streaming videos on YouTube where our team will be monitoring and engaging with comments throughout the week. But also with a new experiment we're launching today called Chrome Dev Summit Adventure. A playful online world where you, the virtual attendees, can interact as we try to recapture some of the joy of face-to-face interactions. We'll talk more about it later today and look forward to hearing what you think about it. The Chrome team at Google has a two-fold mission. First, strengthening the web and other open ecosystems by contributing to open-source projects such as the Blink Web Rendering Engine, the V8 JavaScript Runtime, the AV1 Media Codec, the Scea Graphics Library and developer tools like Workbox, Lighthouse and of course DevTools and more. And these projects are used far beyond Chrome and even the web. They help power countless other products and platforms like the Node.js ecosystem with V8, OpenVideo with AV1 and Scea, which plays a critical role in Android and Flutter. Now the second part of our mission is of course building the Chrome web browser, providing a top quality web experience across Windows, Mac OS, Linux and Android. And on iOS, we bring as much of that experience as we can to millions of users using Apple's WebKit framework. Across all of these efforts, our focus is pretty simple. It boils down to three things. Ensuring the web delivers a safe and secure environment. Making the web browsing experience faster and more seamless. And adding more capabilities to the web, enabling richer and more diverse applications on the platform. In this keynote, we're going to give you an update on our progress and highlight the work that others in the community are doing as well. First, let's transition over to our colleague, Parisa Tabriz, to give us an update on the Chrome browser. Thanks, Dion. 2020 has been a year of challenges and new experiences for all of us. Back in March, we decided to skip a Chrome release for the first time in our history because we wanted to make sure that everyone had a stable, performing Chrome as our team transitioned to work from home. Now, we're proud and humbled that so many people around the world choose Chrome to help them stay connected and informed, especially in challenging times. Reflecting on the year, I want to share some of the ways that we've seen Chrome usage change, how our core principles have helped us be prepared for this shift, and how we continue to build improvements to help users. Now, people around the world relied on Chrome to virtually see and stay connected with their family, friends, classmates, and colleagues. Since January, time spent video conferencing on Chrome on desktop is up by 4x. And we know that performance is key, especially when using video on the web. So to keep Chrome fast and efficient, we introduced profile-guided optimization, which results in up to 10% faster page loads. We also launched tab throttling, and that helps speed up just about everything. Chrome startup, tab switching, tab restoring. And it does this by prioritizing your laptop's resources to the tabs that you're actually using. So this will also reduce power consumption and improve battery life. And finally, we've also made some progress on memory savings, which you'll hear more about from Dion later. Now, when we look to Google search trends data, we see that queries related to health, news, science, government, and food all increased during lockdown. As people look to stay safe, get updates on local restrictions, and just learn how to cook at home. More generally, having access to information on the open web is so critical. And we continue to focus on product inclusion and serving the diversity of our global user base. For those who are low vision or who rely on a screen reader, Chrome became the first browser to create accessible PDFs with auto-generated headers, links, and tables. All of that makes PDFs more legible for screen readers. We've also made it easier to translate entire sites to your preferred language and added support for 28 additional languages. Lastly, we've begun testing a visual based search, which we hope can help users that are new to the internet or who have low or no literacy. As many of us shifted to working from home and all that comes with that, smaller screens, juggling work and home commitments, and so much multitasking, the Chrome team has continued to prioritize productivity features. Tab groups make it easier to organize your tabs by project, urgency, or, well, anyway you like. And you can even collapse tab groups to just get them out of the way. We're also beginning experiments to add new modules to Chrome's new tab page to help you quickly jump back into a previous task, whether it was researching a product, planning a meal, or catching up on your favorite shows. Now, we're conscious of the increase in pandemic-related phishing attacks and other online security threats, and we're proud of both how Chrome has protected users and some new features we launched this year to make it that much harder for online attackers. For example, we've launched an additional layer of security with enhanced safe browsing, more secure and private DNS over HTTPS, and many password manager improvements. We've also delivered more accessible and intuitive privacy controls, starting with the redesign of Chrome settings. And for users that want an additional piece of mind, we introduced a new safety check within Chrome, and we're now rolling out quick access to some of the most used privacy and security controls, like deleting your browsing history or opening an incognito window directly into your address bar. Finally, we've continued to make progress on some ambitious ecosystem safety initiatives. You'll hear later today about the progress we've made on the Privacy Sandbox, which is an open-source initiative to develop a set of open standards to fundamentally improve privacy on the web. And Dion will announce a major update on our work with extensions. As we give users more control over the data shared with their favorite extensions, we want to give you the tools to get ready for this new reality. Now, before I hand it back over to Dion, I'd like to just conclude by acknowledging the Chrome team's really hard work this year, all while being at home, to make our users experience better, releasing eight stable Chrome builds, meeting default browser requirements for iOS 14, and improving performance, helpfulness, and security in Chrome across all platforms that's available. Thank you so much. And now, back to Dion to tell you more about the latest and greatest in the world of Chrome extensions. Thanks, Parisa. A lot of great improvements, and really excited to see everything we're doing to make the browser more efficient, secure, and more privacy-preserving. Now, we think extensions are a superpower for the web, an aftermarket that allows first and third parties to add rich capabilities that can enhance a site or the entire experience of the web. We love the extensions you've built, with over 200,000 active developers and over 250,000 extensions in the Chrome Web Store. And users love them, too. Fun fact, we estimate that users have installed over 20,000 extensions just in the minutes since this keynote began. And users have an expectation now of strong privacy and security guarantees, and we really agree with that. So we've been working on updating our extensions platform to better align with our vision for a more private and secure browsing experience. We call this Manifest V3, and today we're announcing the official release. So for improved security, we'll start with disallowing remotely hosted code and provide developers with more tools to write secure extensions. To enhance user privacy, earlier this year we made controls more visible in the new extensions menu, with some sensitive permissions made optional. Users today can turn off those permissions after the extension is installed. In 2021, we'll go a step further by withholding these permissions by default and giving users the option to grant them at extension install time. Manifest V3 is available to experiment within Chrome 88 Beta, and updated extensions could be submitted to the Chrome Web Store starting January 19th when Chrome 88 hits stable. You can learn more at the link mentioned here. As Dion explained, privacy is a major theme of Chrome's new extensions model. We've also been collaborating with many others in the ecosystem to improve the privacy of the web platform itself. We've been working on a major initiative called the Privacy Sandbox. It's organized into two tracks. First, reducing the cross-site tracking that happens on today's web, and second, enhancing the web with new capabilities that form privacy-preserving alternatives that can power tomorrow's experiences. Some websites use third-party cookies to track people across the web. While Chrome plans to phase out third-party cookies once these privacy-preserving alternatives are in place, we've made cookies more secure for websites and users today. This year, Chrome finished rolling out a new policy known as SameSite, which limits cookies to first-party access by default, requiring developers to declare which cookies can be sent to third-party domains. Before this change, most cookies could be accessed by third parties even when they were only intended for first-party use, needlessly exposing them to security threats such as cross-site request forgery attacks. Now, 99.9% of those first-party cookies are automatically restricted to first-party use in Chrome, and all third-party cookies must be sent via HTTPS, encrypting them in transport. Microsoft Edge and Mozilla Firefox are also in the process of adopting this new SameSite policy. We've been working to address covert tracking, such as browser fingerprinting as well. Now, this occurs when developers attempt to create a unique profile of your browser, a so-called fingerprint, that can be observed across websites. With a new project called Privacy Budget, we're experimenting with a new way to enable rich web functionality while also severely constraining fingerprinting. We also launched the User Agent Client Hints API, which is an alternative to the User Agent Strings that we all know and love going back to the beginning of the web. This enables developers to request only the data that they truly need about your browser. In the second Privacy Sandbox Track, we've been working with the web ecosystem on a new family of web standards that provide privacy-preserving solutions to accomplish important web use cases, such as personalized content, single sign-on and relevant ads, without the need for third-party cookies or other cross-site tracking mechanisms. I'm happy to share that the first two solutions are available for early experimentation by developers. This includes the Conversion Measurement API, a new capability that measures when an ad click leads to a conversion without using cross-site identifiers, and Trust Tokens, a new API to help combat fraud and distinguish bots from humans by conveying trust from one context to another without passive tracking. Both of these are available for testing and feedback via Chrome's Origin Trials mechanism in our current Chrome Stable release. We'll be going deeper into some of these changes later today, so don't forget to catch these sessions. Users are only a low-friction tap away from the next great experience, and they traverse the web link by link. To make that journey great, we all have to ensure that our web pages load fast. Once loaded, we want the UI to feel responsive and buttery smooth. Now, achieving fast loading and runtime performance requires that the browser and web developers work together to do the right things. Earlier, Parisa shared how Chrome is getting updates like profile guided optimizations and tab throttling. In addition, we've also been optimizing memory utilization overall, and have made some really substantial progress here that we want to share. For example, the prior stable release of Chrome, Chrome 85, introduced enhancements to how the browser reclaims memory, that resulted in up to a gigabyte of reduced memory usage for power users on macOS. Our next release, Chrome 87, is showing savings of up to 80 megs for each top site. And we recently updated VA with a memory compression technique that reduces the JavaScript memory footprint significantly. This can be seen here with Gmail, which benefited with a 45% memory reduction. Finally, VA is now able to load a page's JavaScript files in parallel, so scripts can be parsed and compiled and ready to execute as soon as they're needed by the page, eliminating parsing pauses entirely. Now, we're also continuing our work to make it easier for web developers to do their part to create high-performance websites. Earlier this year, we launched Web Vitals, providing clear unified guidance of the attributes for web page that are essential to delivering a great user experience on the web. We focused the program on highlighting three aspects of performance, referred to as Core Web Vitals. The Chrome User Experience report shows that the majority of sites have good interactivity, and nearly half are fast-loading and visually stable. Overall, about a quarter of all sites parcel three metric thresholds, so we've still got a way to go, but we think it's a great start. Now, we dive into this data much more in the Web Almanac, which is launching its new 2020 edition today, authored by experts from across the web. I actually always love finding some absurd stats in there. For example, the longest image all attribute that we found is over 50 million characters long, which is enough to write War and Peace five times. Let's get back to Vitals. Last month, the Google Search team announced their plan over the next six months to incorporate Core Web Vitals into their process for measuring web page performance. So if you value discovery via Google Search, this provides an extra incentive to optimize your Vitals and reach the three thresholds. So get started now. We've got all of the tools to support you as you measure, track, and improve. And the ROM provider ecosystem has moved really quickly here, too. Core Web Vitals is now available to you if you use Cloudflare, New Relic, M-Pulse by Akamai, SpeedCurve, Caliber, and many more. But we also know that many sites are currently using Google Analytics and they want to be able to measure Web Vitals there. Last summer, we released the Web Vitals JavaScript Library, along with instructions on how to collect Web Vitals data and send it to Google Analytics. Now we're excited to launch the Web Vitals report, an open-source website and tool to let you query and visualize your Web Vitals metric data writing Google Analytics. This report also allows you to compare data across segments so you can see how much performance affects your business results. Now we're seeing the Web Vitals approach really resonate with developers, particularly in markets where network infrastructure conditions and device capabilities can be a little bit variable. So what does it take for you to do the work to improve your Vitals? Well, to share an experience of taking a site and iterating on it to meet these thresholds, please welcome Sunit Jindal, principal engineer from Nica. India's leading online marketplace for beauty and wellness products. Over to you, Sunit. Thanks, Dion. I am Sunit Jindal, principal engineer at Nica. India's leading omnichannel beauty destination at Nica. Our belief is that a highly-performance application is a prerequisite for a great user experience, especially for mobile users. One of the things that we have found key for performance success is to be fully aligned with our business-focused teams. How soon the content is rendered to the users, possible benefit in SEO and conversion rates are some of the metrics on which we ensure alignment with our marketing and business counterparts. When Web Vitals were first announced, to be honest, it meant extra work for us, but we also knew that this was a positive change. Although the new metrics meant that we again had to dig deeper to meet the thresholds, but once we did it, it was worth the effort. We improved each of the three core Web Vitals by making optimizations within our core, adding the right CDN where needed, replacing bulky third-party scripts with lighter implementation and much more. As a result, we managed to improve all our core Web Vitals within a few months of working on them. For our users, pages loaded even faster and there are minimal or no content shifts on the page. We also saw a continuous uptick in our performance-related scores across devices and network bandwidth. Post-migration, our page views per visit increased by upwards of 23% as compared to our old mobile site. The traffic from Tier 2 and Tier 3 cities also increased by nearly 28% and finally, we've seen an uptick in our other key metrics as well like average order value and search traffic. Having led my team through this journey, I feel that core Web Vitals stand for a guideline that promotes us to provide a crisp and fast UX. We are happy with the outcome so far and look forward to what's next in the Web Vitals program. Thank you and back to you, Dion. Thanks to feedback from partners like Sunir and the developer community at large. We found opportunities to refine the core Web Vitals' 2020 metrics and how they're measured. Watch Annie's talk later today to learn about how we're thinking about this and how you can share your feedback as we iterate on the metrics set for 2021. You want to be able to create fast, responsive and beautiful UI as easily as possible. You gave us copious feedback on areas of CSS that you wanted to make simpler. Unir is going to share some of the recent changes that target this feedback as well as giving you a peek at some new work that we're particularly excited about. Thanks, Dion. There are so many exciting things going on in the CSS world right now and I have a lot to update you all on when it comes to making UIs easier to build and debug. We've been analyzing trends and conducting surveys and have found that styling has actually been a really big pain point for a lot of you building Web Interfaces. And we hear you as a Web community. We want to fix the issues developers struggle with today. So what have we done recently? Well, first, we've been improving tooling along with our friends at Microsoft by introducing grid dev tools and working on Flexbox tooling to hopefully relieve some of those layout debugging woes. We're also working on a lot of other small incremental changes that will make it more clear what values are being calculated and why. This year, we also launched some pretty key updates for CSS. We've had some major strides in Flexbox cross browser behavior and shipped gap in Flexbox, meaning you can now have parent driven control over the space between your children just like you can with CSS Grid. We're shipping aspect ratio to ensure consistent ratio sizing of your responsive content without hacks and we shipped content visibility, a CSS feature that can significantly improve rendering performance by skipping an elements rendering work including layout and painting until it's needed. This allows for faster interactions with on-screen content with that content still being searchable and accessible. Along with external contributors and help from the Agalia team, we also shipped a few styling APIs including list bullet styling with the marker pseudo elements, more refined text decoration styles, the focus within pseudo class which enables the ability to style a parent based on if it's children are being focused, path support within clip path to support a wider variety of clipping effects and soon we're shipping hardware accelerated SVG animations to ensure better performance across browsers. Another feature I'm excited about is app property which shipped in Chromium 85. You can now register CSS custom properties with syntax and fallback values directly in your CSS files. This is a part of the CSS Houdini effort, specifically the properties and values API. If you're interested in extending CSS with Houdini even further, look out for my talk all about using Houdini in today's browsers including a tool my team built to make it a little bit easier. And if you're watching this talk later, the link will be below. The feature is also looking extra bright for CSS lately. Moving into the coming year, the Chromium team is going to be focusing on bigger picture frustrations for web styling. Along with the open UI community group, we're committed to exploring form control styling and expanding the current set of possibilities for web form extensibility which many struggle with today. We're working on shipping animation timeline to enable scroll linked animations to be styled with CSS, an operation that's currently a pretty heavy lift with JavaScript, and we're looking into how we can make CSS architecture more clear for design systems and products including cascade layers to enable a new injection point for style sheets between the user agent and author styles. We're also looking into CSS nesting, a favorite from PMPost processors as well as scope styles natively in CSS. Soon, we'll be shipping is and where matches selectors for more clear CSS statements when targeting multiple or longer selectors. And finally, the Chromium team is currently exploring container queries, also known as element queries. We're actively prototyping what may soon become a game changer for component driven design, enabling elements themselves to respond to the size of their parent container wherever that is on the page and not just the documents view port size. This is a massive shift in styling capabilities and something I can see really changing the ecosystem to help usher in an era of more individually responsive design components and systems. All of these improvements coming to the web are exciting in their own right, but together they really tell the story of UI styling becoming a priority on the web platform. We hear you and I can't wait to see the CSS and the web evolve from here. Thanks, Yuna. I can't wait to see the rich fluid experiences that you'll build with these improvements. Now later at the event, we'll be talking about how content can be taken to the next level via web stories and more because we're seeing a real surge in creativity as we visualize stories in new ways with creators using rich new tools. And there's another critical aspect of seamless, reducing the friction that users encounter as they transact on the web. We continue to invest here in areas such as identity and payments. With one-time passcode support, or Web OTP, users no longer have to copy and paste from their SMS app when using two-step verification, and this works with Chrome and Safari. Now Web Authent brought biometric sensors to the web, and with Safari recently added in support, Touch ID and Face ID are accessible to the web. We want to bring this level of simplicity to payments, and we're experimenting with secure payment confirmation, which brings Web Authent to payment flows. And we're experimenting right, have started to really explore here, and we can't wait to see the result of these enhanced payment experiences. So check out the sessions and the code labs that will walk you through using some of these APIs. We build these UI features and the capabilities for identity and payments to enable you to build more powerful and rich web applications. You know, we've seen what happens when we lack certain capabilities that you need. You may have to resort to using systems to let you use your HTML, CSS, and JavaScript skills, but now you've had to give up the core benefit of web deployment. Being able to reach users on any platform, on any screen, and without the overhead of forcing a large app download that a user might actually seldom use are all things that make the web such a successful platform. Growing the success of the web means pushing the envelope, unlocking new use cases that are not even possible today, while maintaining the traits that make the web great. Developers like Henrik, who I've actually known in the web community for many years now, are doing just that. So I asked him to join us to share some of his recent work that has a real human impact. Henrik, thanks for joining us. Hey, Dion, thanks so much for having me. I sure wish we could be doing this in person, though. I know, me too. So can you share what you've been building with us? Sure. So any time you put somebody to sleep in a medical setting, it's considered best practice to, you know, keep them alive. I would hope so. So I guess you'd have to monitor the patient's real vital signs. And here we mean human vitals, not web vitals for once. Yeah, exactly. So you have to produce something called an anesthesia record. And part of that record is a chart that shows what the patient's vitals are every five minutes throughout the case. And sometimes the case goes really long, so you might do that 50 times during a given case. And a lot of people are still doing this on paper and producing these little charts like this. And so naturally we built a progressive web app at anesthesiachartting.com that actually does all this for you. Got it. So I'm actually trying to look at that paper, trying to kind of visualize how that PWA would work. Yeah, it's probably easier if I just show you. You can show us? Okay, please. So as you can see, I'm all hooked up to a patient vitals monitor over here. And not only are we able to read the data directly off of that and put it in the chart, we're actually able to issue commands as well. And we had some fun with the speech recognition API. So if I say something like, take a blood pressure now, you notice it actually starts the blood pressure cup here on the monitor. And instead of just having a little vitals monitor off in the corner, we can actually put all this data, including my ECG waveforms and everything up on a big screen. And that way the provider can see everything they need to. That's great. There's a lot going on here. Can you kind of chat about how you get all of these integrations working? Yeah. So we're talking a custom binary protocol that the vitals monitor expects over web serial. We're, of course, using the presentation API to be able to display all this content up on a separate screen that's different from what I'm looking at here. And then we're also using the wake lock API to make sure that this computer doesn't fall asleep on us right in the middle of the case. Absolutely. So why did you build this with WebTek? So distributing software on the web is just so much easier. We actually do have an Electron app that we're using to do some of this. Some of the monitors actually require TCP connections locally. And it's great that that exists. But it also means that, you know, a lot of actually our support headaches come from that because people don't understand they need to go download something and they're not sure whether they're running in Chrome. We're running it separately. And so just be really nice to be able to do it all with web. That makes total sense. Well, it's great to see how this is used in a real world environment. What's next here? And are there any other APIs you'd love to see from the web? Yeah. So as I mentioned, you know, I'm really looking forward to that native Sockets API because that would let us do, you know, talk to some of these other monitors over TCP. And in addition, I think the only thing that doesn't work offline right now in our app is the at the very end when we generate a PDF for you. So we actually run a puppeteer service that will take that HTML and give you a PDF back. It'd be really awesome if we could just generate that PDF in a consistent way, just using a JavaScript API locally. Sounds great. Yeah. Feedback noted. So I really do hope that we can actually chat in person at the next CDS, although it was pretty special to be able to visit you at a dentist office. And this is coming from a Brit. Yeah. No, it was really great. Thank you so much for having me. And just so everyone knows, we took all the necessary COVID precautions here as well. I even took a COVID test yesterday just to be sure we're safe. Safety first. Listening to stories like Henrik's makes us proud of the work we've all done to bring new web capabilities through initiatives like Project Fugu. While Henrik's use case may be a little specialized, there are so many other use cases that you've told us are important. For example, Gravit Designer made it easy for their users to read and write files using the File System Access APIs, simplifying the open and save experience. And they've already started working on the new local font access API, which enables their users to use specialized fonts that are installed on their own computer. We want to hear about the capabilities that you need to boost your web experience. So please keep them coming. And when you bring this all together, you can create something special. We're super excited to share that Adobe Spark recently launched an impressive new PWA. It's performant, capable, and allows next-generation creatives to collaborate and co-create seamlessly. It's a pleasure to use. Hear more from Spark as they share their journey directly in our partner spotlight talk, which is right after this. When you put in the work to build great web experiences, you want to reach as many users as possible. Services like Google Search are a fantastic platform for discovery and a powerful differentiator for the web. However, today, many users are habituated to discovering things through app stores like Google Play. Developers who build a progressive web app that meets the recommended quality bar can incorporate it into an Android app using a trusted web activity. And in Chrome 85, released earlier this year, we extended the support for trusted web activities to Chrome OS, and developers can now also publish their apps to the Chrome OS Play Store. Chrome OS and Chromebooks are a great platform to showcase the power of the modern web and its expanding capabilities via Project Fugu and other efforts. Web apps there get seamless discovery and installation via the Play Store, and they're also able to deeply integrate into the Chrome OS launcher and the overall system experience. Over the past year, Chrome OS has welcomed many powerful new desktop PWAs into its ecosystem from advanced graphics products like Adobe Spark to engaging media apps like YouTube TV and Hulu. Framer, a cross-device design and prototyping tool that was initially a single platform app on Mac OS, was able to increase their user base by four times after releasing their collaborative web version. Today, we're announcing that Google Play is adding play billing support for PWAs published in the Play Store that use trusted web activity. This integration will be live in Chrome 88, available now in the developer channel, and going stable in mid-January 2021. It'll be supported on both Chrome OS and Android, and enables both purchasing digital goods and subscriptions, including the new standardized digital goods API. You can learn more in these sessions on next-level web apps for desktop and what's new for web apps in Play. Now we've shared the platform updates. Let's discuss what's new with our developer tools and how they can help you build these great web apps. Over to you, Jessalyn. Thanks, Dion. There's a lot happening in the world of developer tools. So let me dive right in. To start with, we've got some great new features in Chrome DevTools. First off, Grid Toolings. As you heard from Yuna earlier, you can now debug CSS Grid much more easily with the new CSS Grid debugging tools. Yay, I'm particularly excited about this one. Secondly, we have added new emulations to the rendering and sensors tab, including missing local fonts, inactive users, and much more. Next up, the most used panel in DevTools, the Elements panel, will now support many more features, including style editing for CSS in JS frameworks. In accessibility, we have added a few new features, including accessible color suggestions and emulate vision deficiencies among others. And finally, we have added a bunch of new tabs and panels, such as the new media panel, to help you debug your site with a lot more ease. And there's much more. So don't forget to catch my What's New in DevTools session tomorrow. Moving on, with the increased focus on web vitals, we have seen as much as a 70% increase in growth across all our insights to over the summer. So we are making sure that we continue to make further enhancements to all of them, including Lighthouse, our tool that lets you audit your site in the lab environment and provide actionable guidance on how to improve. First off, we have added three new audits to help you identify specific ways to keep your cumulative layout shift in check. Additionally, we know that third-party libraries have a huge impact on your core web vitals. So as a first step, we have added additional audits for third-party embates to help you clearly understand their impact on your site's metrics. We hope these changes will enable developers to debug and optimize their core web vitals with much more ease. Watch Elizabeth's session later today on the State of Speed Tooling to learn more. Finally, I wanted to give a quick shout-out to the Workbox team who launched more flexible integrations with Create React App, giving you full control over your service worker logic. And more recently, the team announced Bookbox V6, which is packed with some awesome updates, including new extensibility hopes for building custom caching strategies and plugins. It also has support for Webpack V5 and a more flexible integration in Create React App V4. Finally, we have migrated even more of the codebase to TypeScript, making it easier to use from within your TypeScript projects. Don't forget to watch Jeffrey's session tomorrow for the rest. And with that, back to you, Dion and Ben. So we've talked about how to build fast, powerful, and safe web experiences and shown you some examples, but we're always looking to walk the walk ourselves. You know, we ask ourselves, can we create a rich web application that's fast to load and smooth to run? And given who we are, we often end up trying to pull this off with the developer tool. We announced Squoosh two years ago, a Chrome Dev Summit 2018. And with the web about to get three awesome new image formats, we knew it was time to build version two. So we added JPEG XL, WebP2, AVIF, so you can start seeing how far image codecs have evolved in the last two decades. At the same time, we're making use of the latest and greatest WebAssembly features and more mature WebAssembly toolchains, making image compression go much faster in your browser. We've also asked our users what they need, resulting in a new and improved UI, and we wrote a Squoosh CLI, allowing you to compress many images all at once with all the codecs and settings that are available in the PWA. He was so productive to share the same WebAssembly binaries in the browser and node for the command line version. So check out Squoosh V2, and you can read about how the team built it and how you can use it to squish down your images at the link here. Now, as we mentioned at the beginning, the Chrome team is focused on working with the community, which includes all of you virtually here at CDS to make the Web more powerful, faster and more seamless, and above all, safe. It can be dizzying just how fast the Web continues to evolve over 30 years into the platform. I think that's older than most of our team. Are we even allowed to say that? And we've continued to improve Web.dev as your one stop for understanding our perspectives on how to get the best results out of the modern Web. With tools like Lighthouse and the Web Vitals program explained fully on the site. And of course, during CDS Online this week, we'll be doing our best to explain all of the latest and greatest developments and we're available to answer your questions and hear your thoughts and feedback. We have so much great content to share and bonus deep dive material that'll be available on our YouTube channel. So next up, stay tuned to hear directly from the Adobe Spark team on how they built that lovely new PWA we got a glimpse of earlier. Now, we're off to watch two and join you over in the Chrome Dev Summit adventure.