Starbucks

Starbucks published hard numbers: post-PWA, web orders matched native-app conversion (within 10%), web daily active users doubled, and the PWA install was 200KB versus the native app's ~146MB. The headline statistic — a 99.84% size reduction with no conversion loss — became the definitive proof that PWAs could replace native apps for transactional use cases. Every subsequent PWA pitch (Twitter Lite, Pinterest, Trivago, Tinder Online) referenced Starbucks as the proof-point that web could match native for commerce.

Yes — using the Starbucks PWA is free. You pay for the coffee, not the app. The PWA is the same product as the native iOS and Android apps: order ahead, manage Starbucks Rewards stars, reload your card, redeem gift cards. The only commercial dimension is the loyalty program itself (free to join, you earn stars on purchases). The PWA does not have ads. The reason Starbucks built a PWA is that the native app was too large for users in emerging markets and on older devices, where the native install was a conversion blocker.

The PWA is 99.84% smaller (200KB vs ~146MB) and ships the same core features: mobile ordering, store finder, rewards. The native app has deeper integrations: Apple Pay one-tap, Apple Watch ordering, push notifications more reliable on iOS, and richer animations. The PWA installs in seconds even on 2G and works on devices where the native app refuses to install (low-storage Android, ChromeOS, KaiOS). For most users in the US the native app is the default; for users in emerging markets and on shared computers, the PWA is the better fit.

Partially. The service worker caches the app shell, the menu data and your last-viewed store, so you can browse the menu and review your saved cart offline. You cannot place a new order or reload your card without a connection (those require server confirmation and payment processing). The offline mode is useful for browsing the menu on a plane or in a basement, and for re-opening the app quickly without re-downloading the shell.

The Starbucks PWA was originally built by the Starbucks engineering team with Formidable Labs as an outside consulting partner in 2017. It uses React with a service-worker-based PWA shell, Workbox for caching, and a GraphQL backend. The architecture became a case study at Chrome Dev Summit 2017 and Reactathon. It has been iterated since but remains React-based. The team has talked publicly about using PWABuilder-style techniques to keep parity between PWA and native experiences.