Back to Business, resuming all work operations with new guidelines in place.
Let a Kaizen Designer create your online presence.
Progressive — Works for every user, regardless of browser choice, using progressive enhancement principles.
Responsive — Fits any form factor: desktop, mobile, tablet, or forms yet to emerge.
Faster after initial loading - After the initial loading has finished, the same content and page elements do not have to be re-downloaded each time. Ordinary websites often already made use of the browser cache to avoid re-downloading the same data redundantly. But on progressive web applications, the same elements do not need to be re-rendered again.
Connectivity independent — Service workers allow offline uses, or on low quality networks.
App-like — Feels like an app to the user with app-style interactions and navigation.
Fresh — Always up-to-date due to the service worker update process.
Safe — Served via HTTPS to prevent snooping and ensure content hasn't been tampered with.
Discoverable — Identifiable as an “application” by manifest.json] and service worker registration, and discoverable by search engines.
Re-engageable — Ability to use push notifications to maintain engagement with the user.
Installable — Provides home-screen icons without the use of an App Store.
Linkable — Can easily be shared via a URL.
The technical baseline criteria for a site to be considered a progressive web app by browsers were described by Russell in a follow-up post:
Originate from a secure origin. Served over TLS and green padlock displays (no active mixed content).
Load while offline (even if only a custom offline page). By implication, this means that progressive web apps require service workers.
Reference a web app manifest with at least the four key properties: name, short_name, start_url, and display (with a value of standalone or full-screen)
An icon at least 144×144 large in PNG format Use of vector graphics that are indefinitely scalable and require smaller file sizes.