 Hi, everyone. Hi, hi, hi, hi. So my name is Warat Bhoomani Gyat. Oh, sirs, I never hear myself like this before. This is a little bit weird. So my page job is a sheet product officer of the company called Y-Size. We do the social network data analytics. But it's not about decision. So another side of my job, I am the Google Developer Expert in web technology. So for like seven years since 2016, I go around the Southeast Asia to endorse the people to adopt the Progressive Web App to their websites. Today's session is a little bit conflicts with my interest and a little bit conflicts with my faith about Progressive Web App. So for a while, I theorized the Progressive Web App doesn't work with the workplace. So today I will tell you why you don't need the Progressive Web App to your workplace size. So if Google see the record, he will try to email me and say, hey, what are you saying? But it's fine. First of all, what is the workplace? What is the Progressive Web App or the PWA? The Progressive Web Apps is a concept that one, the web can be the app. So the main three things that should be happened on the Progressive Web App is first one is capability. So it's capable. You can access the features of the platform like hardware, like some native dialogue, some things. Second one is variable. So actually this one is talking about web should be run in the offline mode. That means even no internet connections, the web should be able to run at least the catching or something. The last one is most important part of the PWA is installable. So if you ask something about what's different between app and web, means one thing is web cannot install without the PWA setting up. So the PWA mainly talking about installable. So this one is one of the reasons why you don't need it. So these are capturing of the main functions. So that is a concept, right? So these are how it looks like when your web is provided the PWA capability. Third one is about notifications so your web can trigger notifications. Second one is installable when you go in Android, when you go to the website and that website has ability for installations. So it's popup is coming up so you can see the detail and you can install. And also the offline one. So actually with the current technology of the web, you can provide the offline experience to the user by catching some things with something called a service worker. That three stuff that I can call it should be happened in the PWA. And with some requirements right now, offline is required if your website need the user to be installed. So when you go to the workplace side, plugin side has many, many of the PWA plugin. So I try to see what is how many active site that install like the big fold or the big five, the PWA plugin. Right now, I think it's like about 10K sites. Has already provided the PWA experience by the plugin. So yeah, we have some small for the plugin or not a plugin, but that may be very small number. So all of the plugins provide mainly, I think mainly only one thing is installable. So it just made the web can be installed. So maybe some of them provide the offline experience, but not all the work here. Some of the plugin is created by the Google open sort. I can't remember this one or this one, but yeah, either one is provided by the Google. So the questions that is a topic for today is why we don't need it. First one, ask yourself why we need to install the content website on a phone? Why? You go to the one new site, you install it? No way. For me, I don't do that. All in nine applications open like previously every day. Do you think you can be the one of nine? That's not right. It can't be even like your applications force the user to use this. So yeah, I think this problem is like a world problem of any app. But this is actual thing is about the type of the website. So I think mainly of the workplace user provide the workplace as a content website. I can't say that workplace can do only content website because workplace has very wide ability to improve reservations or many things. But I think the majority of the workplace size is the content website. So do you think people love to install that? Pick up your phone and see how many the contents on new sites that OK, I can say. I want to say how many new applications on your phones, like the new publisher. So for me, for my phones, I have only one. It's a medium. The medium is not actually content. It's a platform. So actually, I have zero of that. I don't have any content applications, not talking about a website. I don't have any content applications on my phone. So that's the first thing that people don't want. And I don't think you need to make your website become the PWA. The second one, people love the notifications. I mean the developer and owner of the site because you want to push the content to the user phone to let them read the content. But ask yourself, it's a very simple one, how many applications that you try to silence the notifications? Many of it. Even if you have a lot of notifications, you always click the key or the buttons. You don't read it all. You see it's not very important, like a bang, like there are bus schedules, something like that. So for the content sites, for the very long, long-term implementations, that doesn't work. Also, when the website improvement notification a lot, Chrome's Google tried to block the notification by default. Right now, if your website got blocked from user a lot, Google not tell how much. Chrome will be automatically block your notification by default. So you need the user to activate it before getting notifications. So it's really the chance of your site to find the notification to the user. So it doesn't work. The notification thing doesn't work in the real world for content website. So I read the notification only chat, maybe car broken or something, that's not about content. Safari, when I do the dislike, Safari still not support notification. But just yesterday, the new beta version of the Safari does support the notifications. And also, you need to add to home screen that website before the using notifications. It will be come with a 16.4, maybe. I'm not sure, 16.4 Safari in the next list. So we're waiting for a long, long time, maybe almost six year for web notification on the Safari. But today has happened. But you have to remember this slide again. Notification for the web content, it doesn't work. It doesn't work. No one read it. The conversion rate is very low. Sorry, I have no data back up that how low it is. But for my slightly survey, it's very low. OK, the next one is the offline mechanic. It doesn't decide for the workplace. Why? OK, the offline mechanic of the website is run by something called ServitWorker. So technically, it's like a proxy one. If it has a network request, it cache all the asset on the ServitWorker, on the cache. And when the network cutting down, the browser normally will call the request passed to the ServitWorker. So if the ServitWorker can detect that network is not available, it will serve the cache. So when you are the single-page application, like React or Vue.js or Angular, technically, the ServitWorker will cache only the JS file and some asset file. That's all. So it's very small size. And also, the single-page application is provide the routing in the client size, not the routing. The routing is not in the server side, like workplace. So they do not want to cache all the routings or the part of the application because the routing logic is in JavaScript in the client size. But workplace is not. Your part logical, like Slab Roba Slab Roba, is from your server. So technically, if you are the workplace, it cache all your part every time that you open the new page. So it should make the cache very huge because it's caching all the output that output from the workplace. So in the user side, they've got the huge size of the caching. And also, it's not can provide a good offline experience because they have to cache a static size like you install a caching plugin in the workplace that cache everything as a HTML. It's the same, but it happened in the client side. So it doesn't get very bad because a service worker decides for the single-page applications. So in that case, it's cache only single file of JS, single file of CLS, and the image and all that. What placement you install a lot of the plugin, it cache all the plugin that you install. So that's not good with the client, so they use a lot of the storage. So the next question is, do your sites need to integrate with the platform? You need this? You need the shortcut? No. You need the hardware access to your website? No. You need the Camiller? You need the GPS? No. I think one thing that you need is the share dialogs. So right now, if you call the navigator, dot share it will be pop up the share dialog. I think this is all in one platform feature that you need on your website, but less of it, no. So when you need the PWA, there are questions. There are big, big questions, big wins. The PWA is the way to replace the native applications much as possible. So yeah, I can say PWA cannot fully replace the native application. It's just like maybe 60%, 70%, maybe 80%. Depends on your use case, but it cannot. But if your website is not provide the app experience, the PWA capability doesn't need for your website. I don't want to against like, OK, if you're installed with players, you must not do the PWA. But you have to think first. You have to think that your website is trying to provide an app-like experience or not. If yes, yeah, you should have. But if no, don't try to install the silly back-ins on your website. Make the user have to cache the 20 or 30 megabytes of your page or maybe have to get the notifications every day. So it's like the best experience. So how about the WooCommerce? So the WooCommerce, for me, is very deep pain. Because some of the websites is an e-commerce website, and they are providing the ability of PWA. So I add to home screen like Aliex Place, like Adidas, something. So back to the simple questions. If your websites try to provide the applications experience, do it. It's very good. But if not, don't do it. So yeah, for me, if you are the e-commerce website, I slightly recommend you to do this. Because you want the user to get notification when other updates, notification when shipping has come to homes, the new promotions. And also, you need the user to come back and try to buy the new stuff every day. So for the e-commerce website, it's very good. But in case if you need, like in that case, like e-commerce in the app, or you provide an application-like experience, so you need to consider. First of all, don't install the plugin. Try to get the hard code as much as possible if you are able to do that. So because the plugin try to provide many things and also provide a lot of the code, so it makes your website a little bit slow. Because actually when you want to do the installations, you need only this one. You need only the one JSON. They call it benefit.json. That makes your website has an installation ability. Yeah, it looks scary because it's very long. But actually, you need only this name and the icon that all you want. You don't need other stuff. So these are full versions of the manifest.json. So I forgot to put the names of the file because I just finished a slide a couple of minutes ago. Yeah, but you need only a few lines of the text and make your website installable. Second one is icon must be nice. When user use Android and they add to home screen, the icon will be just inside this circle or inside some shape of it. So use a feature called markable icon to make the icon look very good. Don't try to put icons straightforward. So it makes your icons of your PWAs look same of that. Next one is provide more details about the installation. So PWAs not have a store. User need to read everything, see the demos or screenshots, provide all stuff in the manifest.json. It will help the user to understand about your application is better. OK, app shortcut is a good toy. For me, it's like you can put, if you are the e-commerce side, you can set the shortcut like order standard, new promotions, everything is very helpful. But it doesn't work in iOS yet. But in Macs, in Windows, it's already worked. And yeah, be careful with every time when you provide the offline. Actually, for me, I don't recommend you to provide full offline capability because it's very lack is that user has no internet and try to open the app. So how about like, open your website on the airplane, try to shopping something? Nothing. It's impossible, right? So yeah, try to be careful in cash. Only the page that you want, the user want to see. This is all of that. Again, not the application on the web, it doesn't work. If you are trying to push your content, stop do it. And if you want to push an application about the other status or anything, keep do it. So that is a trick one. And last question, make sure that your user want to install your site on the phone. If you provide this feature without any confidence, then the user will install. Don't do it. Thank you so much. This is all the answer of the big questions. Why you don't need the PWA for your website. Thank you so much. Thank you so much.