Progressive web applications

From Wikipedia, the free encyclopedia
  (Redirected from Progressive web app)
Jump to navigation Jump to search

Progressive web applications (PWAs) are web applications that load like regular web pages or websites but can offer the user functionality such as working offline, push notifications, and device hardware access traditionally available only to native applications. PWAs combine the flexibility of the web with the experience of a native application.

Background[edit]

Since around 2005 web development technologies have shifted from static to dynamic web pages driven by server (PHP, ASP.NET) or client side (Ajax)[1] tools, and responsive web design.[2]

Despite apps based on these technologies on devices such as the 2007 iPhone, attempts at web apps failed by comparison to native apps. Native apps provided a better user experience and booted faster compared to having to load in a browser at runtime. Packaged resources and direct access to hardware allowed native apps to perform much faster to provide more features. By mid 2010, however, continued enhancements in HTML5, CSS3, and JavaScript, significantly more capable and standard-compliant web browsers, along with powerful processors such as the Apple A10 and Snapdragon 820 made hybrid-apps a viable alternative.

Characteristics[edit]

In 2015, designer Frances Berriman and Google Chrome engineer Alex Russell coined the term "progressive web apps"[3] to describe apps taking advantage of new features supported by modern browsers, including service workers and web app manifests, that let users upgrade web apps to progressive web applications in their native operating system (OS). According to Google Developers,[3][4][5] these characteristics are:

  • Progressive — Work for every user, regardless of browser choice because they're built with progressive enhancement as a core tenet.
  • Responsive — Fit any form factor: desktop, mobile, tablet, or forms yet to emerge.
  • Connectivity independentService workers allow work offline, or on low quality networks.
  • App-like — Feel like an app to the user with app-style interactions and navigation.
  • Fresh — Always up-to-date thanks to the service worker update process.
  • Safe — Served via HTTPS to prevent snooping and ensure content hasn't been tampered with.
  • Discoverable — Are identifiable as “applications” thanks to W3C manifests[6] and service worker registration scope allowing search engines to find them.
  • Re-engageable — Make re-engagement easy through features like push notifications.
  • Installable — Allow users to “keep” apps they find most useful on their home screen without the hassle of an app store.
  • Linkable — Easily shared via a URL and do not require complex installation.

Progressive web apps are an enhancement of existing web technology. As such, they do not require separate bundling or distribution. Publication of a progressive web app is as it would be for any other web page. PWAs work in any browser, but "app-like" features such as being independent of connectivity, install to home screen and push messaging depend on browser support. As of April 2018, those features are supported to varying degrees by the Microsoft Edge, Google Chrome, Mozilla Firefox and Safari browsers, but more browsers may support the features needed in the future.[7][8]

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:[9]

  • 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 fullscreen)
  • An icon at least 144×144 large in png format. E.g.: "icons": [ { "src": "/images/icon-144.png", "sizes": "144x144", "type": "image/png" } ]

Technologies[edit]

Commonly used technologies serve to create progressive web apps in the broad sense[10][11][12] are the following:

Manifest[edit]

The web app manifest is a W3C specification defining a JSON-based manifest[6] to provide developers a centralized place to put metadata associated with a web application including:

  • The name of the web application
  • Links to the web app icons or image objects
  • The preferred URL to launch or open the web app
  • The web app configuration data for a number of characteristics
  • Declaration for default orientation of the web app
  • The option to set the display mode, e.g. full screen

This metadata is crucial for an app to be added to a home screen or otherwise listed alongside native apps.

AppCache (obsolete)[edit]

An earlier technology to support offline use of the web.[13] It works adequately for the use case it was designed for (single-page application), but fails in problematic ways for wikis and other multi-page apps.[14] Currently supported by major browsers and in use for years by some sites, but will eventually be removed.

Service workers[edit]

Native mobile apps deliver rich experiences and high performance, purchased at the expense of storage space, lack of real-time updates, and low search engine visibility. Traditional web apps suffer from the inverse set of factors: lack of a native compiled executable, along with dependence on unreliable and potentially slow web connectivity. Service workers are used in an attempt to give progressive web apps the best of both these worlds.[15]

Technically, service workers provide a scriptable network proxy in the web browser to manage the web/HTTP requests programmatically. The service workers lie between the network and device to supply the content. They are capable of using the cache mechanisms efficiently and allow error-free behavior during offline periods.

Properties of service workers:

  1. Triggered and kept alive by the relationship to the events, not by the documents
  2. Generic in nature
  3. Event-driven with time limited scripting contexts and running at the origin
  4. With natural endpoints for a wide range of runtime services
  5. Have a state
  6. With a script URL
  7. Containing registration
  8. Allocated ID or UUID
  9. With lifecycle events
  10. Have a script resource map
  11. Can skip waiting for the flags

Benefits of service workers:

  • Capable of handling the push notification easily
  • Synchronise data in the background
  • Capable of responding to resource requests originating elsewhere
  • Receive centralized updates

Web workers[edit]

Allows a web app to run multiple threads of (JavaScript) code simultaneously.[16] Thus, long activities can be moved off the user-interface thread, keeping responses snappy. They have a close relationship with service workers, but are more widely supported.

WebAssembly[edit]

Allows precompiled code to run in a web browser, at near-native speed. [17] Thus, libraries written in languages such as C can be added to web apps. Due to the cost of passing data from JavaScript to WebAssembly, near-term uses will be mainly number-crunching (such as voice recognition and computer vision), rather than whole applications.

Indexed Database API[edit]

Indexed Database API is a W3C standard API for interacting with a NoSQL database. The API is supported by modern browsers and enables storage of JSON objects and any structures representable as a string.[18]

Web Storage[edit]

Web Storage is a W3C standard API that enables key-value storage in modern browsers. The API consists of two objects, sessionStorage (that enables session-only storage that gets wiped upon browser session end) and localStorage (that enables storage that persists across sessions).[19]

Application shell architecture[edit]

Some progressive web apps use an architectural approach called the App Shell Model.[20] For rapid loading, service workers store the Basic User Interface or "shell" of the responsive web design web application. This shell provides an initial static frame, a layout or architecture into which content can be loaded progressively as well as dynamically, allowing users to engage with the app despite varying degrees of web connectivity. The shell can be stored locally in the browser cache of the mobile device.[21]

Directories and examples[edit]

  • Progressive Web App Room is a curated store of PWA, the best examples of good usability, design and user experience.
  • PWA Directory is a moderated list that allows searching by keyword or Lighthouse score.[22]
  • The Microsoft Store contains "PWAs" packaged for Windows 10, but does not appear to contain links to actual on-line PWAs. It's not clear that it can list web apps separate from Windows apps.
  • Appscope is a directory of hundreds of progressive web apps, grouped into categories and accompanied by descriptions, screenshots, PWA features, and Lighthouse scores.

The audit validates the aspects of a PWA, as specified by Google's baseline PWA Checklist

References[edit]

  1. ^ Garrett, Jesse James. "Ajax: A New Approach to Web Applications". Retrieved February 18, 2005.
  2. ^ Marcotte, Ethan. "Responsive Web Design". Retrieved May 25, 2010.
  3. ^ a b Russell, Alex. "Progressive Web Apps: Escaping Tabs Without Losing Our Soul". Retrieved June 15, 2015.
  4. ^ "Your First Progressive Web App | Web Fundamentals - Google Developers". Your First Progressive Web App | Web Fundamentals - Google Developers. Retrieved 2016-07-17.
  5. ^ Google Developers. "Progressive Web App". Retrieved June 15, 2015.
  6. ^ a b W3C “Web App Manifest”, Working Draft, retrieved 12 September 2016
  7. ^ "Can I use pwa?". CanIUse. Retrieved 14 August 2018.
  8. ^ "Is Service Worker Ready?". Jake Archibald.
  9. ^ Russell, Alex. "What, Exactly, Makes a Progressive Web App". Retrieved October 18, 2016.
  10. ^ "Discoverable". Mozilla Developer Network. Retrieved 2017-04-24.
  11. ^ "Network independent". Mozilla Developer Network. Retrieved 2017-04-24.
  12. ^ "Instant Loading Web Apps with an Application Shell Architecture". Google Developers. Retrieved 2017-04-24.
  13. ^ "Using the application cache". MDN. Mozilla. Retrieved 14 August 2018.
  14. ^ "Application Cache is a Douchebag". A List Apart. Retrieved 14 August 2018.
  15. ^ "Learn Everything About Progressive Web Apps".
  16. ^ "Worker". MDN. Retrieved 14 August 2018.
  17. ^ "WebAssembly Concepts". MDN. Retrieved 14 August 2018.
  18. ^ "Concepts behind IndexedDB". MDN. Retrieved 14 August 2018.
  19. ^ "Web Storage API". MDN. Retrieved 14 August 2018.
  20. ^ "The App Shell Model".
  21. ^ "Progressive Web Apps – a Quality Mix of Web and Mobile".
  22. ^ "Lighthouse - Google Developers".