Progressive Web Applications (PWA)

PWA's are the future of mobile apps and the web. With features such as adding to home screen, offline support, push notifications and more, a PWA offers a user experience approaching that of a native mobile app. We have at one time or another have been promted to install a PWA when browsing a website. This feature is implemented by mobile browsers that using information found in the websites web manifest and uses the information stored there to allow offline browsing and interaction like any other device specific application. Don't worry if most of that didn't make sense. We will explain them a bit more.

Do I need a PWA?

This is a very good question. Progressive web applications aren't useful for every business model.

How does a PWA work?

Progressive web applications are becoming the standard due to their ability to be device independent, updated automatically and contain native functionality. Thanks to HTML5 becoming standard Steve Jobs's original vision for a world without plugins is becoming a reality.

PWA Components

When a mobile user navigates to your website "Add to home screen" (or a2hs for short) is a feature implemented by mobile browsers that takes the information found in an app's web manifest and uses them to represent the app on the device's home screen with an icon and name

The Manifest

Rarely in tech lingo is there a term that is as concise as "manifest". A manifest is exactly as it sounds. A progressive web application manifest

We have at least 5 key things that need to happen. 1. A link in the head pointing to your manifest ex. manifest.json 2. A JS script service worker located in the root. 3. A a JS page that initiates the sw.js maybe located in a common js file.