 Welcome everyone, welcome to the Chrome Dev Summit. We're so excited to be here. Very happy to be able to share our enthusiasm, all the excitement about the web ecosystem with you and talk across these two days about all the things we're doing to help you be successful building for the web, about all the things we're doing in Chrome. Very excited. So let's get into it. So our mission on Chrome, our mission is to move the web platform forward. This is as true today as it was when we first got started with Chrome nearly 10 years ago. And so we're very excited about that. Like I said, over the next two days we're going to have a lot of content for you, a lot of great stuff talking about how we're working to try to make the web better and work with you to create great experiences on the web. Now, ordinarily, at the beginning of these talks, we usually update you on the number of Chrome users. In fact, last time at Google I.O., we mentioned that there was over a million Chrome mobile users, which is awesome. There's been tremendous growth. This year, I want to present a slightly different number. This year, I want to share, or sorry, not this year. It was the same year. But at this moment, I want to share that we have over 2 billion active Chrome browsers. This is across mobile and desktop. So rather than focus on one platform, I wanted to make this point that there are just a lot of Chrome browsers out there. And well, that's great for us and everything. I don't mean for you to be excited about that. I think what's exciting about this to you all is that when you're thinking about building for the web, this means there's a lot of browsers out there that implement the latest web standards and implement all the latest and greatest features that when we're talking about how to build for the web, how to take advantage of these new things, that's reality. You can actually take advantage of that. There's a lot of users out there with modern browsers. And it's not just Chrome. There's lots of other browsers that are implementing the latest standards, too. There's a lot of energy and excitement in this whole space, which is really, really great to see. I think it's fantastic. And so it all gets to the point that the web has tremendous reach. We know this. This is why it's such an attractive platform. It's such a cost-effective, low-friction way to get experiences in front of users, again, in front of real people. And that low-friction is all made possible because of links, URLs. That's the superpower of the web, right? We're very used to that. And the links are getting even more exciting. So I wanted to invite you to pull out your phone. If you have an Android phone or if you have Chrome on your iPhone, there's beacons in this room, Bluetooth beacons. So make sure you have Bluetooth turned on. And if you're on an iPhone, you don't have Chrome set up, right? You can check this URL here. It'll give you instructions. But the point is, the physical web made possible because of Bluetooth beacons and your Android device observing those beacons and sending URLs out into this room, URLs that are contextually interesting to you. So in this case, there's a beacon broadcasting the URL for the Chrome Dev Summit web app. So it makes it very convenient. This is sort of leaning on the power of URLs. As a user, you can just quickly go under the notification shade on Android, click on the physical web entries there, find yourself on an experience. There's not much hassle to that. It's really great. Now, there's another beacon in the room for an app called Polymon, a web app called Polymon. This was created by the Polymer project, Polymer Team. So Polymon is a free-to-play, location-based, augmented reality game that uses your mobile device's GPS capability to locate, capture, battle, and train virtual creatures called Polymon. That sounds kind of familiar, right? Anyways, so you collect Polymon by locating members of the Polymer team in the real world in this conference venue. So check it out. It's really cool. It's a lot of fun. So like I said, contrast that seamlessness, that ease of finding yourself on experiences, thanks to the web, with the cost of installing software. That friction really matters. So by some estimates, every interaction step that you expect a user to take in order to get to your experience can cost you up to 20% of your potential users. Think about that for a moment. Compare one tap to, say, three taps. That means you're potentially losing about a third of your users. Or imagine four taps versus one tap. Now you're potentially losing half your users, roughly. And so that's a big deal, right? We all know this. That's why we're all here. We're excited about the web. We know this potential. It's real. It's awesome. And so the web is really great on mobile. We've been very focused on the mobile web for some time. And of course, the web didn't grow up with mobile being a reality. But the web has been awesome for the web. And it has really helped expand the whole market for the web. Making it so much more easy to reach users. Think about it. You have a mobile phone in your pocket. The fact that you can sit on your couch and not have to get up off the couch to grab the laptop, but you can just pull out the phone, browse the web, access all this wealth of information, shop for things, et cetera. It's so convenient. Just recently, I pulled out my phone, my Nexus phone, and I bought a Pixel phone. It was so easy. Of course, now there's a delay, probably, but anyways. Anyhow, of course, we know that the web has lots of challenges. It wasn't, again, built with all of that in mind, with a mobile in mind. And all these challenges, these constraints, have led to innovation, really. And we've all, as a community, had to figure out mobile. And we've made a lot of progress. So there's going to be a lot talking about that. And of course, the mobile web has evolved a lot from the early days. And this is a charge, just a reminder. I think most folks are familiar with this, that mobile web usage has, what is that? Anyways, mobile web usage has far eclipsed desktop web usage. This is going back a couple of years. And so I'm sure many web developers are familiar with this, and it means building for mobile web is a priority. And mobile web brings with it so many challenges. Of course, mobile devices are vast and very different screen sizes, CPU constraints, memory constraints, power constraints, all manner of constraints, and of course, connectivity constraints. We're all familiar with the good old offline dinosaur, right? And of course, connectivity constraints are not just about reliability. They're also about bandwidth and latency. And some of these challenges are extremely acute for a lot of your users, because 2G networks are a reality for many people in the world. And if you look at developing markets, it's even more of an issue. Nearly two thirds of users in developing markets are stuck behind 2G connections. That's a big deal. Infrastructure's improving, but we don't expect this 2G to go away anytime soon. It'll still be with us. So there's a lot of challenges there to address 2G. And the web itself, you know, the whole point here is that the web is a very big thing. It's worldwide. It's in the name. It's everywhere. It's a wonderful tool for so many users. There's easily over 3 billion users across the whole world using the internet. That's like 10 times the size of the US. So if you think about it, there's just a large, addressable population. And nearly 2 billion of those are in developing countries. So we look at current estimates of internet users. We see that, well, there's roughly about 280 million in the US, about double that in India, about 460. And in China, upwards of 720 million. So the web is truly global. There's a lot of users all over the place. And if you look at just the growth last year, a lot of it's concentrated in places like India, where India saw about 30% growth, over 100 million new users coming online, that's really remarkable. That's 10x the growth of China, 100 times the growth in the rest of the world. And emerging markets is where a lot of the new growth is going to come from as well. Just focusing on India, for example, 65% of that population of that country is not yet online. That's 860 million potential new users. 20 times the number of users not yet online in the US. And so I think, actually, the reason why I make a focal point of India is not just that there's a lot of users there, but actually that we're seeing some of the most interesting and remarkable web development happening in India. And the reason for that is because a lot of these users who are connecting to the internet for the first time are doing so, not from a laptop, they're doing it from a phone, a phone that is very underwhelming by what many of us are used to. These are phones with 512 megabytes RAM at most, very limited screen sizes, very underwhelming CPUs, already mentioned memory, limited storage. A lot of these users, they don't have a PC where they're going and backing up their data. That phone, that phone, there's the computing device. That's where they're storing information that they care about. It's not easy for them to install another app. In fact, it's very common. You talk to people, they say, I went and installed that, use it for a little bit, and then uninstalled it so I could have that precious, precious storage space for something else. So we're seeing a lot of innovation in this area because it turns out the web is actually a fantastic tool. Think about it, the web is designed, it's a streaming platform. You can bring part of your experience down incrementally. It's designed for constrained storage. It's great for constrained networks, actually. And thanks to a lot of the new APIs that have been going into the platform, we're enabling developers to have a lot more control over how their web experience works, how they can deliver the experience and how they can create a good experience for users. And we're going to talk a lot more about that. So there's just a lot of innovation happening here out of the need to address those constraints. And it's really that necessity that is leading to so much innovation. And I think it's really exciting. And so my point, really, is that web apps work really well in emerging markets. They also work really well here. And all the approaches, techniques, and technologies that have been developed that are working for folks in India, they work really well here, too. I think we all know what it's like to have poor connectivity. But we also know what it's like to have LTE. So this is the point. Web works really well in emerging markets. A year or so ago, we had early pioneers in this space like Flipkart showing the way, developing lightweight web experiences that could incrementally come down onto the device, be cached, and deliver delightful experiences to users behind 2G connections. Other companies have been embracing this approach as well. One that I want to highlight is Vute Media, a Vute streaming, video streaming service. This comes from Viacom 18, which is a joint venture between Viacom and Network 18. So they just set up, this is a new service. And they got online very recently. They built a web experience. In fact, 40% of their traffic goes through the web. And by building for the web, they were able to really reach a lot more users more easily. And in fact, just getting started here, it took them only a matter of three weeks to prototype an experience that they were happy with and that convinced them that they should continue to invest. And they are investing further. The next version will feature offline caching of snippets of videos so that users can preview movies and TV shows and other Vute originals easily. So that's very exciting. So this is all about building progressive web apps. I think many of you have all heard this term before. We've been talking about it for a while. We introduced it last year. And progressive web apps are not just about any one technology or any set of technologies. It's not even about anything like that. It's more about a new way of thinking about building web experiences, web experiences that are radically improving the user experience. And we're going to be talking a lot about this. But these experiences that you can create, the thing that I want to show you and have you leave with, is knowing that you can create experiences that are just as immersive, just as engaging, just as native feeling as any experience you expect to find on your phone. I think that's really exciting, combining the power of the web with the form factor of mobile and creating experiences that really delight users and that you get a lot of value out of. And so there's a lot of different companies joining in and seeing success. And we're going to be talking about a variety of these over the course of these two days. But I'd like to just zero in on one and take a moment to show you a demo. So this is about CNET. CNET has built an experience at CNET.com slash tech dash today. It's a progressive web app. And so let me demo that for you. So I'm going to switch over to the overhead here. So I have my snazzy new Pixel phone. And I have CNET tech today added to my home screen. So I'm going to launch it. And it comes up smoothly. Nice little transition there. So we're scrolling, of course. This is a little carousel, so I can browse different articles. Oh, trying not to read the news too much. So anyways, you saw that was all very smooth, fluid, fast as what you'd expect on a mobile device. You might have might notice that I'm on airplane mode. That's pretty cool, right? Maybe you thought I already had Chrome running or something like that. So I'm going to just let's get rid of that. And let's do it again. Same thing you saw before. It's pretty cool, right? Just in case you didn't have any doubts, that was just a website. I added it to my home screen. Anyways, thank you. Let's go back to the slides. So really great to see the work that folks like CNET are doing, but they're definitely not alone. Excuse me. Another partner that we're going to talk about is Alibaba. And Alibaba is one of the world's largest business to business platform in over 200 countries. So they built a progressive web app over the summer. And they're seeing 76% increase in conversions. And this is about users interacting with support when they're interested in a product. So it's very exciting. That's a huge key metric for them. And seeing that kind of increase is significant. And I want to just make the point real for you. So Singles Day is an event that Alibaba sees is an event in China a day where lots of shopping happens. This is an event where people feel encouraged to buy something for themselves. And the Singles Day happens on November 11th, 1111, which, if you adjust for time zones, is right now. And this is the biggest shopping event on the internet. And they expect to see nearly $20 billion in revenue, which is three times more than Black Friday and Cyber Monday combined. So investing in a progressive web app was a big deal for them, a significant thing. And seeing these kind of conversion rates is a big deal. So I think it's great to see folks having this kind of success building for the web, building for the mobile web. And Taltran will be up shortly after me to share more partner stories with you. So progressive web apps. I've talked about this before, like I said. And we've been defining them as reliable, fast, and engaging. The point is progressive web apps are about creating a much better user experience, like what I showed you with the CNET Tech Today example. And by reliable, I mean things like, well, you saw how I was offline and I tapped a home screen icon, the experience should work, right? That's what a user expects. That's the point. And when you think about fast, this is a great stat. It comes from a double-click study where they found that users abandoned. 53% of users abandoned sites that take longer than three seconds to load. Interesting thing about this is that a year ago, that number would have been 40%. So users obviously don't have the patience that you might wish they had. And so it's really important to pay attention to that initial loading experience. And you saw with the CNET example that it was very nice. And so all this is made possible thanks to the Service Worker API. But it's not just a Service Worker API. It's about using it properly. And we're going to talk a lot about that. But the Service Worker API, just to refresh you, is an API that lets you have control over your caching strategy and offline approach to building your experience. So you can manage how the network is used by your web app. And that is really a huge enabler for the web platform. And we estimate about 3% to 4% of all page loads in Chrome are now going through Service Workers, which is really cool. So focusing on performance. This is another way of looking at it. And I really like this quote. It comes from a member of our team. If you wouldn't make eye contact with a stranger, for the time it takes you, takes your web app to first paint, it's too slow. So this is getting at that sort of awkwardness of like, well, I'm waiting, I'm waiting, what's happening? And first paint, that's about getting some pixels on the screen, drawing something. There's no reason why that can't be done quickly. There's lots of challenges, of course. But we want to show you how to be successful at that. And it's not just about getting some pixels on the screen. It's also about making that experience interactive shortly thereafter. And so with that in mind, you're going to hear us talk a lot about this metric, getting your site interactive within five seconds over a 3G connection. Again, not everyone is lucky enough to have an LTE connection. So focusing on 3G seems to make sense. And if you have an LTE connection, you should be able to do a lot better than this. But five seconds is a great metric that we're going to talk a lot about. And this is made possible thanks to things like Service Worker, but that sort of leads to designing your web application better, chunking it up better. But there's other technologies like HTTP 2.0, which are a big enabler here. And oh, by the way, Service Worker API requires TLS. And HTTP 2 brings TLS. So these things all work together very nicely. We're very excited about these technologies and helping you achieve these kinds of goals and build fast experiences for the web. So when it comes to engaging, you saw how I had a website on my home screen. It was an engaging experience. Normally, what you expect from the mobile web, well, you expect that it's easy for users to land on your site. It's so easy thanks to the power of URLs for users to discover content. But what about getting back to that content that they liked? Well, oftentimes, that means the user might have to remember to think to bookmark your site or remember the origin or remember all the steps that got them there. Of course, when it comes to mobile, that's nowhere near as effective as just getting your icon on the home screen. So a year ago, we focused on this problem. And we introduced app manifests and an ability for the website to indicate that it would be great to prompt the user to get them to add the site to the home screen. And this has been a great feature. You think about add to home screen as a lightweight install. That's the experience that I showed you there. And on Chrome, or sorry, we've seen from partners a lot of great success from add to home screen. This stat comes from Alibaba, which I was talking about earlier. They've seen four times more engagement with Alibaba thanks to add to home screen for users who have added Alibaba to their home screen. So that makes sense. It's not actually surprising. It's good to see it borne out like this. So add to home screen is an important thing. We know that intuitively. And indeed, it is based on the data we're seeing. We've also been tuning add to home screen. So we've been playing with the heuristics. One of the things we didn't want to do was just spam these prompts in front of any user any time. We want to be thoughtful about it. So we've been tuning them and seeing, by tuning them, by reducing the amount of engagement required on the site before we show the prompt, actually getting 48% more conversions or installs or users adding these sites to their home screen. Which is a really great stat. And all without actually increasing the number of users who ignore the prompt or dismiss the prompt. So we feel like there's a lot of opportunity here to continue refining. And so just want you to know from the Chrome team's perspective, we're working to tune this and make it work even better. We're also playing around with different formats. Why not call it install, actually? And so we're definitely experimenting with that. I think there's some interesting questions here, but it's exciting to try. And I'm really excited to share that we're also looking at experimenting with deeper integration into the Android OS. And this is really cool. So today, the way Add to Home Screen works is it's putting a widget on your Android device. And what that means is the user, if they remove that, they're not gonna find the app, the icon in the all apps. And that can be confusing. So we're working to improve that so that when you go through the Add to Home Screen flow, what it actually will mean is that your website will actually be available in all apps. It'll be in places where you expect to find app icons on the device. This has been a big effort. There's a lot of work still to do. We're experimenting with this. It's gonna be in preview shortly on the Chrome Dev Channel for very, very excited about this change. And some of the other things that go along with it are things like giving you the ability to update the icon and change the name of the thing that's been pinned to the Home Screen, which is a really obvious thing that you should be able to do. And then also we're experimenting with granting notification permission when the user goes through the Add to Home Screen flow. That's something that a user actually is used to when they think about the way Android permissions work. So we're just looking to smooth out the rough edges here, make the experience work a lot better. I'm very excited to share that. And Paul Kenlon will be up here a little bit later talking more about this change. So the other big way that the developers like to reengage with users on the phones is with push notifications. This is something that we've been working on for a while, been seeing a lot of adoption. It's a really key feature, think about it. Users who are interested in getting notifications, it's a great way to remind them that there's interesting content on your site. And there's been a lot of adoption. So 18 billion push notifications sent daily, which is a big number. Things is exciting, but even more exciting. So we've seen over 50,000 domains using push notifications. This is really, really interesting because it sort of speaks to the long tail aspects of the web. The web is really great at enabling the long tail of developers. And just to give one example, this comes from Carnival Cruises. So on Carnival Cruises site, you can book a trip. You can put it on hold. Maybe you're not sure yet if you want to buy it. And then they'll offer a feature to notify you when your hold's about to expire. And they get about a 24% opt-in rate for this. And when the notification appears in front of users, 42% of them actually click on the notification and land back on the Carnival Cruises site. That's a big deal. These are users that they might not have had coming back otherwise. And so a different topic, seamless sign-in. This is something you're gonna hear more about later today. This is about the credential manager API that we introduced back around Google I.O. But now we have some early partner results and I wanna share those with you. In the case of AliExpress, they're seeing an 85% reduction in sign-in failures, which is really cool. And Pinterest seeing about a 10% increase in desktop logins. So these numbers are all about, these are early data, but people are seeing success. And the nice thing about the credential manager API, if you're not familiar with it, is that it's all about avoiding situations where users have to re-enter their username and password because the browser already has that information and we can negotiate a seamless way for it to allow you to log in. And getting logged in and signed in is really important, especially for your engaged users. And we're also gonna talk a lot about payments because we know this is really important part of the web ecosystem. A lot of work's gone into improving payments on the web. We've of course put a lot of effort into autofill improvements in Chrome, but there's also the payment request API, which is all about bringing one tap payment to the web. Very excited about this. Zach will be up later talking about this. So I think it's clear that building progressive web apps makes a lot of sense. There's a ton of value here. It's a lot of work going into improve the platform and make it so that you can be really successful building progressive web apps. And we also wanna take a moment to talk about some of the tools that we're building to help you be successful. And these are just some of the tools that I wanna highlight. We're gonna be talking about these throughout the conference and these tools and others. First is Lighthouse. This is a Chrome extension that we built that helps you zero in on some of the things you could do to improve your progressive web app. It's sort of an analysis tool. It helps you optimize your progressive web app. You'll hear more about this from Paul Irish a little bit later. And the second one is real world condition testing or simulating network and CPU conditions that you might find in the real world. This is a new feature of the DevTools in Chrome. It's very handy, very useful. Of course, there's no real substitute for real actual device testing. A lot of your users do not have fancy new Pixel phones and so on. And so it's important to test with a diversity of phones to make sure you're building an experience that works for everybody. And Alex will be up later talking about how to do that with, again, with DevTools. There's also a new security and application panel in DevTools, which are really handy. You're gonna hear more about these, but they're really helpful to help enable you to explore what's going on with your progressive web app. Being able to explore the cache is really a nice feature. And so the other tool I wanna take a moment to talk about is Polymer. And we've been working on Polymer for a while now. This comes from the Chrome team. We built Polymer in the beginning because we wanted to do it in conjunction, in concert with the improvements to the web platform. And Polymer is all about web components and web components are a new feature of the web platform. We wanted to develop web components the right way. And building Polymer was a way to sort of guide that process from our perspective. And Polymer's great library makes it really easy to build for the mobile web. And that's important. Again, we wanna make it easy for everyone. But web components, of course, there's been quite an arc in the development of web components. The initial versions that we launched in Chrome, they didn't see a lot of adoption from other browser vendors. That's unfortunate. We went back to the drawing board, worked with them in the standards bodies, and today I just pleased to announce that we're seeing a lot of shared enthusiasm for these APIs. In fact, Apple has started shipping some of them, like Shadow DOM V1. This is a big deal. If you're familiar with Polymer, Shadow DOM is the most complicated piece of the whole web components set of technologies. And getting this implemented natively means using web components can be done in a much more lightweight fashion. It's great to see. And even on the tip of tree of WebKit now, custom elements V1 landed. And it's not behind the flag or anything. So it's fantastic to see all this progress. HTML imports will figure it out. And there's a lot of partners adopting Polymer, using it at scale, including many products from Google today, such as YouTube. Really, really excited to see all of these folks seeing success with Polymer. And at the Polymer Summit just a couple of weeks back, we announced Polymer version two, which in addition to being based on these new V1 specs of web components, also is a much lighter weight, faster take on Polymer. We're really excited about it. You're gonna hear a lot more about it later. In addition to Polymer being a library that helps you build web components, we've also fleshed out the whole Polymer a bit more with the Polymer app toolbox to make it easy for you to build applications. A lot of times, this is where folks are struggling. This makes it a lot easier to prototype and build experiences. And really happy to announce that there's been a lot of interest in the community around web components. We have this new site, beta.webcomponents.org, which folks are just pouring in different elements that they've built. So it's a great community site, great opportunity to kind of see what other folks are building and take advantage of these components. Again, the whole point with web components is these are reusable chunks of code. And technology that you can use. So speaking of web components, I also want to talk about AMP. And AMP is another great tool for helping you get on the web and be more successful in the web. And AMP is actually based on web components. It's got a custom markup, which are just web components. There's over 700,000 domains now publishing AMP. So it's seeing a lot of adoption. And this is web components being used at scale. And AMP is, like I said, a great way to get content in front of users. And it can also be a great way to get content in users that leads them into your PWA. Leads them into your progressive web app. And we'll talk a lot more about using AMP and PWAs together tomorrow. So those are some of the tools. Also want to just make a few notes here about predictability. And what I mean by this is, we want to make the web easier. A lot of times, thanks to quite a lot of legacy, there's a lot of little dark corners and so on and challenges for you as you're thinking about targeting a bunch of different browsers. So this is a big focus for us. And our goal really is, like I said at the beginning, to move the whole web forward. And that includes making it one platform as much as we can. And so like I said, the web should just work should just work for you. So we're focused on web standards. We're focusing on working with other browser vendors. This collaborations that we've had are really important. It leads to things like I said with web components and service worker API and so on and so forth. And we're also working to sort of get better at doing new feature incubation and figuring out how to work with the standards community to bring features to market in a better way. So a lot of progress here. Our focus is, like I said, just on making things easier for you. And on that note, I just want to share a tool that we put together, which is this browser bug searcher. It's just a convenient tool. It lets you search bugs across all the different browser engines. I think it can be very handy. So check it out. And so also on the education front, I want to mention that there's been a lot of, so in addition to the Chrome Dev Summit, which your head, and that we had a year ago, we also had the Progressive Web App Summit in the summer. And we've been having these Progressive Web App Roaches, which is taking content, talking about progressive web apps and helping developers be successful. So in fact, we just had one yesterday in San Francisco. Maybe some of you attended it. But this is content and code labs and scripts that you can take and use yourself to put on a Progressive Web App event in case there's not, in case the road show isn't coming to your community. We're also working on longer instructor led education programs on Progressive Web Apps. So look for more of that to come. So looking ahead, I just want to wrap up a little bit by saying that, obviously the web is a big deal. You're all here for a reason. We love the web, right? There's so much energy, so much innovation, so much enthusiasm, a lot of excitement. You can see how this path of figuring out the mobile has gone and how we're accelerating towards, figuring out these wonderful Progressive Web App experiences that can make the experiences so much more delightful for users and help the developers be successful at reaching those users. There's a lot of other new technologies that I didn't mention that are coming to the web and enabling other really exciting opportunities. Think of features like web assembly. There was just a cross browser developer preview announced recently on this. Web assembly is an evolution of Asim.js, which was informed by some of the early work that we did on Native Client. Web assembly combined with WebGL and now WebGL 2.0 bringing OpenGL ES3 to the web. Imagine the kinds of experiences that this can enable, this technology can enable. Obviously things like more immersive games, but a lot of other really cool stuff. I'm very excited about that. And then you combine some of those technologies and the things we're doing with new platforms like VR. Think about web VR and actually the kind of convenience that the web adds and the kind of capabilities it adds to the VR. You have your headset. You want to be able to dig in on something and explore things. And if you have to stop to install apps, it's not going to work great. And so the web is actually a wonderful fit for such an environment. Think about AR, augmented reality. Here you're looking out onto the real world and this is future stuff. Imagine something tagging real objects in real space with not just names and descriptions, but like URLs as you can go and find out more about that object. URL is such a powerful tool in that kind of world. And the web is such a great fit. And I think it's on us to kind of explore and develop and all of us, I mean, to figure out this kind of, figure out how the web can be leveraged in these kinds of environments. Very excited about the possibilities there. And then think about Internet of Things, IoT. You saw earlier the example of physical web to get access to URLs that are contextually relevant to you. But imagine you're walking up to some kind of device and it's broadcasting a URL to you and that URL is the application that you use to control that device. Thanks to APIs like web Bluetooth, you can imagine how that would work, right? You walk up to some kind of a device and it broadcasts a URL. Now you've got the control website and it's talking web Bluetooth to that device and interacting with it. That seamlessness, that low frictionness of the web, it's such a great superpower. You can imagine it in so many other applications. So anyways, these are just some thoughts on that. And I'm excited to see what you all will build and what we'll build together. I'm excited to be part of this ecosystem. I think it's really exciting. Like I said, we have a lot of awesome content for you today and tomorrow. So thank you for being here.