PWA
Web application that behaves like a native app: installable, offline-capable and with push notifications, but built for the browser.
Progressive Web Apps (PWAs) bridge the gap between web and native. They are normal websites that behave like native apps: installable on the home screen, usable offline and with push notifications. Companies like Starbucks, Twitter and Pinterest use PWAs to reach users who do not want or cannot install an app.
What is PWA?
A Progressive Web App (PWA) is a web application that uses modern browser APIs to deliver an app-like experience. Core traits: installable (add to home screen without app store), offline capability (via service workers), push notifications, fast load times and responsive design. PWAs are built with standard web tech (HTML, CSS, JavaScript) and run in any modern browser. They meet criteria such as: progressive, responsive, connectivity-independent, app-like, fresh, safe (HTTPS), discoverable, re-engageable (push), installable and linkable.
How does PWA work?
A PWA rests on three technologies: A service worker (JavaScript running in the background) intercepts network requests and serves cached content when offline. The web app manifest (manifest.json) defines name, icons and launch behaviour for installation. The app shell architecture loads the static shell immediately and fetches content dynamically. HTTPS is required because service workers only work over secure connections.
Practical Examples
Twitter Lite: The PWA is 1–3% of the size of the native app, loads in under 5 seconds even on slow networks and increased engagement by 65%.
Starbucks: The PWA lets customers browse the menu and prepare orders offline; orders are sent when back online.
Pinterest: After moving to a PWA, time on site rose 40% and ad revenue 44% because the barrier without an app store download was lower.
Company wiki: An internal knowledge base as a PWA usable offline on the shop floor without stable Wi-Fi.
Restaurant menu app: A PWA that guests open via QR code without installing an app, with offline caching for fast loading.
Typical Use Cases
Mobile-first websites: Sites that should feel like apps without app store publication
Emerging markets: Regions with slow internet and cost-sensitive devices
Internal tools: Enterprise apps to roll out to various devices without MDM
Content platforms: News, blogs and wikis that should be readable offline
Replacement for simple native apps: Apps that do not need deep hardware or an app store
Advantages and Disadvantages
Advantages
- No app store: No review process, no commission, instant updates
- One codebase: Works on iOS, Android, desktop and any modern browser
- Offline: Service workers enable use without internet
- Small and fast: PWAs are often 10–50x smaller than native apps
- SEO-friendly: PWAs are normal websites and get indexed by search engines
Disadvantages
- iOS limitations: Apple supports PWAs only partially (e.g. limited push, service worker lifetime)
- Limited hardware: Bluetooth, NFC and some sensors are not or only partly available in PWAs
- No app store presence: Users searching in the app store will not find the PWA
- Less trust: Some users trust installed apps more than websites
Frequently Asked Questions about PWA
When is a PWA better than a native app?
Can PWAs send push notifications?
How do you install a PWA?
Related Terms
Want to use PWA in your project?
We are happy to advise you on PWA and find the optimal solution for your requirements. Benefit from our experience across over 200 projects.