 Welcome back to Ask Chrome. We are here for the final episode about Project Fugu. I'm Mariko with Pete. Let's get into the question. So Chernee wanted to know, when you're implementing these new features, what's the best way to go about having fallbacks? Like some people might say progressive enhancement, but what's the best way to use these features without separating completely new set of features? Yeah, that's a really good question. And I think it's really important to, as you think about adding these new APIs to your experience, is that you start with a really good baseline experience that works across all browsers. And then you use these APIs to build on top of that, to progressively enhance the experience and make it better. Users should never get an experience that says, oh, sorry. You can't use this because your browser doesn't support X. And they should definitely not get an experience where it's like, oh, we don't support your browser. All right, so what about like, do you have a specific example of how you go about? Yeah, I think my favorite example to use is the SMS Receiver API because it's a pretty new API. And we've got some very established patterns for using it. So today, with the SMS Receiver API, you typically use an input element with type equals number. The cool thing there is on older browsers that don't support input type equals number, they're going to fall back and just show the standard typical QWERTY keyboard. But on more modern browsers, when they show the keyboard, they're going to show just a numeric keypad. So the user can switch over to their SMS app, get figure out what that OTP is, type that number in, and it's really easy. But with the SMS Receiver API, if it exists, you can say, hey, does this exist? All right, I want you, the browser, to go listen for this incoming SMS. When that SMS arrives, you can grab the OTP from it and just automatically sign the user in. So the user experience there becomes kind of magical, but you haven't blocked anybody from signing in. The same thing exists for things like the native file system API, where you could use the input type equals file to be able to upload files and the download tribute on an anchor tag to be able to download stuff. So users can be able to upload and download files relatively easily from their system. There's a really ugly hack for the WakeLock API to keep the screen awake. I'm not going to tell you how to use it because it's pretty horrible. But with that, there's stuff available. What we want to do is make sure that we're making these experiences much easier for developers so that you can create really great user experiences and really great web apps for your users. I think that's all the questions I have. Thank you, Pete, for joining us, answering your questions. And thank you very much for watching. See you on the next episode of Ask Com.