Sound simple, no ? Well, it’s not that difficult, we’ll do it right now. in a way that it can be used to install the app. The app manifest is a json file that will add metadata information for your app. The Service worker is a script that runs separately from your web page and offers extra functionality, like push notifications and background sync. Now we know how to check if our website is ready for being a PWA, but what does it take to transform it into a PWA? Basically, two things: a Service Worker and a manifest file. If you click on Generate report, it will scan your website to see if you have everything to run your app as a PWA: There is a resource to audit your app, it’s called Lighthouse and can be accessed by opening the Dev Tools (F12):

The full checklist for a PWA can be found here.

It should serve data using HTTPS, not HTTP.

It should be fast, even on slow networks.

It should be launchable and installable.

That seems very nice, no ? And what are the requirements to make a PWA ? That seems too good to be true, but there is more: it can also use the resources of the hosting OS, as a native app and can be sent and distributed in the platform store. A PWA is an app that allows to be installed in the hosting OS, is multiplatform, and doesn’t need the browser to be ran.

One easy way to do it is to transform it into a Progressive Web App (PWA). There are several ways to transform your web app into an installable app, without rewriting it. That would be true some years ago, but not anymore. But a web app is a web app and, as so, it should run in the browser. You have developed your Asp.Net Core MVC, it’s working fine and then you want to take it into the next level: to make it installable and allow it to be distributed in the platform store.

Visual studio code icon png 512x512