Skip to content
Tutorials Center
My learning

Topics

Lesson 1 of 37 ยท Getting Started

What Is a Progressive Web App?

Learn what a Progressive Web App is, how it differs from a normal website and a native app, and why PWAs are installable, reliable and fast on any device.

A Progressive Web App, or PWA, is a website that behaves like an app. It is built with ordinary HTML, CSS and JavaScript and is delivered over the web, but it can be installed to a home screen or desktop, open in its own window, keep working with a bad connection, and even receive notifications. There is no app store review and no separate codebase for each platform. You publish a URL and the browser does the rest.

The word "progressive" is the key idea. A PWA is built so that it works for everyone, and then it gains extra abilities in browsers that support them. A visitor on an old browser still gets a working website. A visitor on a modern phone gets an installable, offline-capable app from the very same code. In this course you will build up those abilities one at a time.

Website, native app or PWA?

Before PWAs, you had two options. A website is easy to reach (just a link) but lives inside a browser tab, usually stops working offline and cannot be launched from the home screen. A native app is installed from a store, works offline and feels at home on the device, but you write it once per platform, pay store fees and ship updates through reviews.

A PWA sits in between:

Website PWA Native app
Reached by link Yes Yes No (store page)
Installable No Yes Yes
Works offline Rarely Yes, if you build it Yes
Push notifications No Yes (most browsers) Yes
One codebase for all platforms Yes Yes No
Updates Instant Instant (with care) Store review
Access to deep device APIs Limited Limited, growing Full

The last row matters. A PWA cannot do everything a native app can. If you need advanced Bluetooth profiles, background location tracking or deep operating system integration, native is still the better choice. For a very large number of products (shops, dashboards, news readers, note-taking tools, forms, games) a PWA is enough.

The three promises of a PWA

Fast Loads quickly and responds instantly to input
Reliable Works on flaky or no network
Installable Lives on the home screen like an app

Reliable, fast and engaging: the goals behind the PWA idea.

1 / 2

The characteristics of a good PWA

People describe a good PWA with a handful of adjectives. You will see them throughout the course.

  • Reliable. It loads even when the network is slow or absent. A service worker answers requests from a cache so the user never sees the browser's "no internet" dinosaur.
  • Fast. It paints quickly and reacts to taps without lag. Performance is measured, not guessed (see the Performance chapter later in the course).
  • Installable. A web app manifest describes the app, and the browser offers an install option.
  • Responsive. The layout adapts to phones, tablets and desktops.
  • Secure. It is served over HTTPS, which is also required for service workers.
  • Discoverable. It is still a website: search engines can index it and people can share its URL.
  • Linkable. Every screen has a URL. No store listing required.
  • Engaging (optional). Push notifications and badges can bring users back, when used with respect.

Real-world examples of the idea

Think of a notes app. As a normal website it needs the network to show anything. As a PWA, the first visit downloads the app's code into a cache. On the second visit, even in airplane mode, the app opens instantly, shows saved notes from local storage and syncs changes once the connection returns. The user can pin it to the home screen and never think about a browser again.

Or think of an online shop. A PWA version can cache product pages the visitor already saw, show a friendly offline page when the connection drops, and let customers re-open their cart from an icon. Store owners often see better engagement because the app loads faster and is one tap away.

The moving parts

Three technologies make a site a PWA, and each gets its own chapter:

  1. A web app manifest, a small JSON file that tells the browser how to present the app.
  2. A service worker, a script that runs in the background, sits between your page and the network and can answer requests from a cache.
  3. HTTPS, because both of the above handle sensitive data and are only enabled on secure origins (plus localhost for development).
flowchart LR
  U["User taps the icon"] --> B["Browser opens the app window"]
  B --> M["Reads the manifest"]
  B --> S["Service worker intercepts requests"]
  S --> C["Cache"]
  S --> N["Network"]

The manifest controls how the app looks and installs. The service worker decides where each response comes from.

Progressive enhancement in code

The "progressive" part is practical. You never assume a feature exists; you test for it first. The runnable example below checks which PWA-related features the current environment offers. The result depends on where the code runs, because the sandbox of this page restricts some of them, which is a good illustration of why feature detection matters.

JS Detect PWA-related features

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Notice that "Standalone display" is false here: you are looking at a normal page in a normal browser. When an installed PWA launches in its own window, that same check becomes true, which lets you tweak the interface for app mode.

Here is a second, tiny pattern you will use constantly: only turn on an enhancement when the feature exists.

JS Enhance only when supported

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Common myths

  • "A PWA is a framework." No. It is a set of web standards. You can build one with plain HTML or any framework.
  • "PWAs only work on Android." They work on desktop Chrome, Edge, Safari and Firefox to different degrees, and on iOS and iPadOS with some limits you will meet in the browser support lesson.
  • "Every website should be a PWA." Not necessarily, but adding a manifest and a basic service worker is cheap and rarely hurts.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does 'progressive' mean in Progressive Web App?

    Progressive enhancement means the basic site works everywhere, and features such as install and offline are added where supported.
  2. 2. Which three pieces make a site a PWA?

    A secure origin, a web app manifest and a service worker are the core of every PWA.
  3. 3. Which task is a PWA still NOT well suited for?

    PWAs have limited access to low-level device features, so very deep integrations still favor native apps.
  4. 4. Why do we check 'serviceWorker' in navigator before registering one?

    Feature detection keeps the site working in browsers without the feature.

Summary

  • A PWA is a website that can be installed, works offline and feels like an app.
  • It sits between a website and a native app: one codebase, reachable by link, no store required.
  • Core ingredients: HTTPS, a web app manifest and a service worker.
  • Always use feature detection so unsupported browsers still get a working site.
  • PWAs are not for every use case, but they cover a very wide range.

Next: The Building Blocks of a PWA