Convincing a customer to download your mobile app is hard. Really hard. The average app loses 77% of its daily active users within the first three days. Users must visit an app store, wait for a download, grant permissions, and create an account—all before they can browse your products.
Progressive Web Apps (PWAs) skip this entire friction funnel. Your online store behaves like a native mobile app—fast loading, offline-capable, installable on the home screen, and able to send push notifications—all without the app store barrier.
Key takeaways:
- PWAs deliver native-app-like speed and offline functionality directly through the browser, with no app store download required
- Major retailers (Alibaba, Lancôme, Flipkart, and others) have reported meaningful conversion and engagement gains after launching PWAs
- Mobile traffic typically outpaces mobile conversions—PWAs are designed to help close that gap
- For most e-commerce use cases, a PWA is cheaper to build and maintain than separate native iOS/Android apps
What Exactly Is a PWA?
A Progressive Web App is a website built with modern web technologies that delivers an experience indistinguishable from a native mobile application. Google coined the term, but PWAs work across all modern browsers and devices.
Your customers don't care whether they're using an app or a website—they care about speed, reliability, and a friction-free experience. PWAs deliver all three.
The three technical pillars of a PWA are:
1. Service Worker
A JavaScript file that runs separately from your main website code, acting as a network proxy. It intercepts network requests, caches critical assets, and enables your site to load even when the user has no internet connection. A customer browsing your products on the MRT underground can still view previously loaded pages, add items to cart, and complete their order when they reconnect.
2. Web App Manifest
A simple JSON file that tells the browser how your PWA should behave when "installed" on a user's device. It defines your app name, icon, splash screen color, and whether it should open fullscreen like a native app.
3. HTTPS
PWAs require a secure connection. This is a feature, not a bug—HTTPS ensures that all data between your PWA and your backend is encrypted.
Why Global Retailers Are Betting on PWAs
Major brands have publicly shared impressive results after launching PWAs:
| Brand | PWA Result |
|---|---|
| Alibaba | 76% increase in conversions across browsers |
| Lancôme | 17% increase in conversions, 53% increase in mobile sessions on iOS |
| West Elm | 15% increase in average time spent on site |
| Flipkart | 40% increase in re-engagement from users who added the PWA to their home screen |
| Trivago | 150% increase in user engagement for users who added the PWA to home screen |
| George (Asda) | 3.8x faster page load time, 31% increase in conversion rate |
The common thread: PWAs deliver native-app performance with the reach of the web. No app store gatekeepers, no download friction, no update hassles.
The Mobile Conversion Gap
Mobile traffic dominates but mobile conversions lag behind desktop. Across e-commerce globally:
- Mobile accounts for 60-70% of traffic.
- Mobile accounts for only 30-40% of conversions.
- The gap represents billions in lost revenue.
Why the gap? Mobile websites are slower, harder to navigate, and subject to network interruptions. Users hesitate to enter payment details on jerky, slow-loading mobile pages. PWAs close this gap by delivering desktop-quality speed and smoothness on mobile devices.
PWA Capabilities That Drive E-Commerce Revenue
Home Screen Installation
When a user visits your PWA multiple times, the browser prompts them to "Add to Home Screen." With one tap, your store icon appears alongside their native apps. No app store visit required. This dramatically increases repeat visit frequency.
Push Notifications
PWAs can send push notifications on Android and (since early 2025) on iOS devices. Cart abandonment reminders, flash sale alerts, order status updates, and personalized product recommendations arrive directly on the user's lock screen—just like a native app.
Offline and Low-Network Browsing
A customer browses your catalog on the train, loses signal in a tunnel, but continues browsing cached product pages. They add items to cart. When they emerge from the tunnel, the PWA syncs the cart and they complete checkout. No native app can do this better.
Instant Loading
After the first visit, the service worker caches the application shell—the HTML, CSS, and JavaScript that form your store's structural skeleton. Subsequent page loads feel instant because the browser isn't downloading the entire page from scratch; it's fetching only the new product data.
PWA vs. Native App: The Honest Comparison
| Feature | PWA | Native App |
|---|---|---|
| Installation | One tap from browser | App Store search, download, permissions |
| Updates | Automatic, seamless | User must manually update |
| Storage on Device | Typically under 5MB | Often 50-200MB+ |
| Offline Functionality | Yes, via service worker caching | Yes, native storage |
| Push Notifications | Yes (Android + iOS now) | Yes |
| Device Hardware Access | Limited (camera, GPS, some sensors) | Full access (Bluetooth, NFC, etc.) |
| Discoverability | Search engines, links, QR codes | App Store search only |
| Development Cost | One codebase for all platforms | Separate iOS and Android builds |
For most e-commerce use cases, the PWA wins on reach, maintenance, and cost-effectiveness. Native apps still excel for experiences requiring deep hardware integration or intensive graphics (like AR try-on or gaming).
Implementing a PWA for Your Store
Shopify Merchants
Shopify's Online Store 2.0 themes don't automatically deliver full PWA functionality, but several paths exist:
- Use a PWA-focused theme from the Shopify Theme Store.
- Implement a headless frontend with Hydrogen + PWA configuration.
- Use third-party PWA plugins that add service worker and manifest capabilities.
WooCommerce and WordPress
Plugins like Super Progressive Web Apps or PWA for WP add PWA capabilities to WooCommerce stores with minimal configuration. Combined with a fast, well-optimized theme, you can achieve near-native performance.
Custom-Built Stores
If you're building on Next.js, the next-pwa package adds service worker generation and precaching with minimal configuration. Combined with Next.js's static generation and edge rendering, you get a PWA-ready, hyper-fast storefront with relatively little extra effort.
The PWA Checklist
To qualify as a PWA and get the "install prompt" from browsers, your site needs:
- Served over HTTPS.
- A valid web app manifest with icons in multiple sizes.
- A registered service worker with offline fallback.
- Fast loading on slow networks (responsive design).
- Each page has a unique URL (linkable and shareable).
Test your site with Google's Lighthouse audit tool. It provides a PWA-specific score and actionable recommendations.
Frequently Asked Questions
Does a PWA replace the need for a native app?
For most e-commerce businesses, yes. PWAs cover the core needs—speed, offline access, push notifications, home screen installation—without the cost of building and maintaining separate iOS and Android apps. Native apps still make sense for businesses needing deep hardware integration, like AR features or advanced camera use.
Will building a PWA slow down my existing website?
No, when implemented correctly a PWA should make your site faster, not slower. The service worker caches assets so repeat visits load near-instantly, and the core requirements (HTTPS, responsive design) are good practice regardless.
How do I know if my current site already qualifies as a PWA?
Run it through Google's Lighthouse audit tool (built into Chrome DevTools). It gives a dedicated PWA score and lists exactly which requirements—manifest, service worker, HTTPS, etc.—are missing.
Conclusion: The Web Is Your App Store
For Malaysian e-commerce businesses, PWAs solve a critical market reality: customers are