I am using my Portfolio Website for the DEMO. You can Use any responsive website for the same.
| Name | DEMO |
| PWA |Ayush's Portfolio |
| PWA |Nilay Das's Portfolio |
| PWA |Rahul Singh's Portfolio |
| PWA |Fauji Travel Agency |
| PWA |Fauji Travel Agency |
- Create an app manifest
- Add it to your base HTML template
- Create the service worker
- Serve the service worker on the root of the scope you used in the manifest
- Add a <script> block to your base HTML template to load the service worker
- Deploy your progressive web app
- Use your progressive web app!
An app Manifest is a JSON file containing the following information:
The canonical name of the website A short version of that name (for icons) The theme color of the website for OS integration The background color of the website for OS integration The URL scope that the progressive web app is limited to The start URL that new instances of the progressive web app will implicitly load A human-readable description Orientation restrictions (it is unwise to change this from "any" without a hard technical limit) Any icons for your website to be used on the home screen (see the above manifest generator for autogenerating icons) This information will be used as the OS-level metadata for your progressive web app when it is installed.
This is a Sample Manifest.json used in my project.
I suggest adding the HTML link for the manifest to the lowest level HTML template of your app, or, in the case of a pure client-side web app, its main index.html file, as it needs to be as visible by the browser client trying to install the app. Adding this is simple. Assuming you are hosting this manifest at the path /static/manifest.json, simply add it to the section:
When service workers are used with the fetch event, you can set up caching of assets and pages as the user browses. This makes content available offline and loads it significantly faster. We are just going to focus on the offline caching features of service workers today instead of automated background sync, because iOS doesn't support background sync yet (although things are moving in a good direction
This is a Sample Service-Worker used in my project.
Copy Paste the Content of script as it is and paste in the bottom of your Html page ( it contains Javascript)
To load the service worker, we just add the following to your base HTML template at the end of your tag:
<script> if (!navigator.serviceWorker.controller) { navigator.serviceWorker.register("/sw.js").then(function(reg) { console.log("Service worker has been registered for scope: " + reg.scope); }); } </script>And then deploy these changes – you should see your service worker posting logs in your browser’s console. If you are testing this from a phone, see platform-specific instructions here for iOS+Safari and here for Chrome+Android.
Deploying your web app is going to be specific to how your app is developed. On firebase or on any server.
Name | Link |
---|---|
PWA | Google Developers |
PWA | Code Lab |
Copyright (c) 2020 Ayush Sharma
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.