What's the difference between a web app and a progressive web app (PWA)?

A plain web app runs in a browser tab: it's great for interactive tasks but needs a connection and sits inside the browser's own interface. A PWA adds three ingredients — a service worker, a web app manifest, and HTTPS — that let the same app be installed to the home screen, cache content so it works offline or on poor networks, load almost instantly on repeat visits, and send push notifications, all without the App Store or Play Store.

Examples make it concrete. Ordinary web apps include Gmail, Trello, and most admin dashboards. Well-known PWAs include Twitter/X Lite, Starbucks, and Flipkart's Lite experience — on a phone they feel much like installed apps, with an icon on the home screen and offline support, even though they're built with web technology.

Choose a PWA when you want app-like convenience — offline access, a home-screen icon, push, and speed for returning users — but don't want the cost and friction of building and maintaining separate iOS and Android apps or pushing people to download from a store. It's a strong fit for e-commerce, booking, content, and tools with repeat visitors. If you need deep hardware access or maximum performance, a native app may still be the better call.