The $200,000 Problem
A restaurant chain with six locations across the GTA came to us last year. They wanted a mobile app for their loyalty program. The quotes they had received for native iOS and Android apps: $180,000 to $240,000 for initial development, plus $3,000 to $5,000 per month for ongoing maintenance across both platforms.
We built them a Progressive Web App for $45,000 that works on every phone, loads in under two seconds, sends push notifications, and works offline. Their customers add it to their home screen directly from the browser. No app store required.
This story repeats itself constantly across Toronto businesses. Companies assume they need native apps when what they actually need is a fast, reliable mobile experience. PWAs deliver that at a fraction of the cost.
What a Progressive Web App Actually Is
A PWA is a website that behaves like a native mobile app. It uses standard web technologies (HTML, CSS, JavaScript) but includes features that were previously exclusive to native applications:
- Home screen installation: Users can add the PWA to their phone's home screen. It appears alongside native apps with its own icon and launch behavior.
- Offline functionality: Service workers cache critical resources so the app continues to function without an internet connection.
- Push notifications: Send notifications to users' devices just like a native app (supported on Android, and now iOS since version 16.4).
- Background sync: Queue actions taken offline and sync them automatically when the connection returns.
- Full-screen experience: When launched from the home screen, PWAs run without the browser address bar, providing an immersive native-like experience.
From a user's perspective, a well-built PWA is indistinguishable from a native app for most use cases.
The Numbers: PWA vs. Native
Here is an honest comparison based on our project data and industry benchmarks:
Development cost:
- Native (iOS + Android): $100,000 - $300,000
- Cross-platform (React Native / Flutter): $60,000 - $180,000
- PWA: $25,000 - $80,000
Development timeline:
- Native (both platforms): 4 - 8 months
- Cross-platform: 3 - 6 months
- PWA: 6 - 14 weeks
Ongoing maintenance:
- Native: $2,000 - $6,000/month (two codebases, app store updates, OS compatibility)
- Cross-platform: $1,500 - $4,000/month
- PWA: $500 - $2,000/month (one codebase, no app store management)
User acquisition:
- Native: Requires app store listing, ASO (App Store Optimization), and convincing users to download
- PWA: Accessible via URL. Share a link and users are in the app. No download barrier.
Who Is Using PWAs Successfully
PWAs are not experimental technology. Major companies have adopted them with measurable results:
- Starbucks: Their PWA is 99.84% smaller than their native iOS app. Daily active users on the PWA doubled.
- Pinterest: After launching their PWA, time spent on the mobile web increased by 40% and ad revenue increased by 44%.
- Uber: The Uber PWA is only 50KB and loads in under 3 seconds on 2G networks, expanding their reach in markets with slower internet.
Closer to home, we are seeing Toronto businesses in food service, professional services, events, and retail adopt PWAs to replace both their mobile websites and their plans for native apps.
When a PWA Is NOT the Right Choice
Honesty matters more than a sale. PWAs are not always the answer. You still need a native app if:
- Heavy device hardware access: Bluetooth LE for medical devices, NFC for complex payment terminals, ARKit/ARCore for advanced augmented reality. Browser APIs are catching up, but some hardware integrations still require native code.
- Intensive graphics or gaming: If your app is a game or involves complex 3D rendering, native development gives you direct access to the GPU that browsers cannot match.
- App store presence is critical: If your business model depends on app store discovery (being found by users browsing the App Store), a native app has an advantage. However, you can list PWAs in the Google Play Store using Trusted Web Activities.
- Complex background processing: Apps that need to run extensive background tasks (like fitness tracking or continuous location monitoring) still work better as native applications.
For roughly 70% of the mobile app projects we evaluate, a PWA meets or exceeds the requirements at significantly lower cost.
The Technical Foundation
For the technically curious, here is what makes a PWA work:
Service Worker
A service worker is a JavaScript file that runs in the background, separate from your web page. It intercepts network requests, manages a cache of resources, and enables offline functionality. Think of it as a programmable proxy between your app and the network.
Web App Manifest
A JSON file that tells the browser how your app should behave when installed. It defines the app name, icons, theme colours, display mode (fullscreen, standalone), and start URL. This is what makes the "Add to Home Screen" experience work.
HTTPS
PWAs require HTTPS. This is non-negotiable. Service workers have access to powerful features (intercepting network requests, managing caches), and HTTPS ensures these capabilities cannot be exploited by third parties.
Building a PWA for Your Toronto Business
The transition to a PWA can happen incrementally. You do not need to rebuild your entire digital presence.
- Start with your existing website: Add a service worker and web app manifest to your current site. This alone enables home screen installation and basic offline support.
- Identify the core mobile use case: What do your customers most need to do on their phones? Focus the PWA experience on that single workflow first.
- Optimize for speed: PWA or not, mobile performance matters. Aim for a Lighthouse performance score above 90 and a Time to Interactive under 3 seconds on 4G.
- Add progressive features: Push notifications, offline forms, background sync. Add these features based on user feedback and actual usage patterns.
The most successful PWAs we have built started small, proved their value with one key feature, and expanded from there.
Looking Ahead
Browser support for PWA features continues to expand. Apple's addition of push notifications and badging to iOS Safari was a turning point. Web Bluetooth, Web NFC, and File System Access APIs are closing the remaining gaps between web and native capabilities.
For Toronto businesses evaluating their mobile strategy, the question is shifting from "should we build an app?" to "do we need a native app, or will a PWA deliver the same result at a third of the cost?"
At Fusion Interactive, we build PWAs using React and Next.js with a focus on performance and user experience. If you are considering a mobile application for your business, let us show you what a PWA can do before you commit to native development costs.
