PWA vs Native App: Which Should Freelance Devs Build for Clients?
Clients ask for "an app." What they usually mean is: "I want something on people's phones." The question is — do they need a native app, or will a Progressive Web App do the job?
For most freelance projects, the answer is PWA. Here's why.
The Cost Comparison
| Factor | Native App | PWA |
|---|---|---|
| Development cost | $15,000–$50,000+ | $0–$5,000 |
| Timeline | 3–6 months | 1–4 weeks |
Results vary. These are illustrative ranges, not guarantees. Your costs depend on scope, market, and client.
| Maintenance | Continuous (OS updates) | Minimal |
| Distribution | App Store approval | Direct URL |
| Offline support | Full | Full (with service worker) |
| Push notifications | iOS + Android | Android only (for now) |
| Home screen install | App Store | Browser prompt |
When to Build a Native App
- Hardware access — Bluetooth, NFC, ARKit, advanced camera features
- Background processing — continuous GPS tracking, audio playback in background
- App Store presence — client specifically wants to be in the App Store / Play Store
- Complex animations — games, 3D rendering, heavy GPU usage
When a PWA is Enough
- Content sites — blogs, portfolios, documentation
- E-commerce — product catalogs, checkout flows
- Tools — calculators, formatters, converters
- Dashboards — admin panels, analytics views
- Business apps — CRM, invoicing, inventory
The Freelancer's Playbook
Here's how to pitch PWAs to clients:
1. Start with the problem, not the technology.
Don't say "let's build a PWA." Say: "Your customers want to access your catalog offline. I can build that in 2 weeks for $3,000."
2. Show the math.
A native app typically costs $20k+ and takes 3 months. A PWA often costs $3k and takes 2 weeks. Both solve the same problem for most use cases. (Typical ranges — your numbers will vary.)
3. Demo the install.
Open a PWA on your phone, tap "Add to Home Screen," and show the client the icon. That's the moment they get it.
4. Mention the upgrade path.
"We can start with a PWA. If you need native features later, we can wrap it in Capacitor or build a native shell."
Real Example: Client Billing App
A client wants an app where contractors log hours and generate invoices. Do they need native?
- No hardware access needed
- No background processing
- Works offline (service worker caches the app)
- Needs to be installable (home screen icon)
PWA is perfect. Build it in a week, deploy to Vercel. No Play Store fees, no approval process. Pricing depends on your market and client.
Want a head start?
TinyCoder is a PWA starter template with 5 offline dev tools. Config-driven — change the app name and colors in one file.
Get TinyCoder — $29The Bottom Line
Native apps are for specific use cases — hardware access, App Store distribution, complex performance. Everything else? PWA.
As a freelancer, PWAs mean faster delivery, lower costs, and happier clients. You ship in weeks, not months. And you still charge premium rates because you're solving a real problem.