Start with the mobile website
Most ecommerce traffic arrives on phones, and most of it through a browser. Before building an app of any kind, ask whether your mobile site is fast, easy to use and accessible. A well-built responsive site beats a mediocre app. Apps are for engaged customers, not for acquiring new ones, since shoppers rarely install an app to buy once.
What each option is
- Progressive web app (PWA). A website with extra capabilities: it can be added to the home screen, work partly offline, load quickly through caching and send web push notifications on supported platforms.
- Native app. An app built for iOS and Android, distributed through app stores, with access to the full range of device features.
- Hybrid or cross-platform app. A single codebase, using frameworks such as React Native or Flutter, compiled into store apps. It sits between the other two on cost and capability.
Comparison
| Factor | PWA | Native or cross-platform app |
|---|---|---|
| Distribution | Link, search, and optional install | App stores, with review and approval |
| Discovery | Findable through search engines | Store search and advertising |
| Development effort | One web codebase | One or two codebases |
| Updates | Instant, on deploy | Store review for releases; users must update |
| Device features | Growing, with differences across browsers and platforms | Full access |
| Push notifications | Supported on many platforms; support and user flows vary | Mature and widely used |
| Offline | Partial, via service workers | Strong |
| Performance | Good with careful engineering | Excellent for rich interactions |
| Payments | Standard web payments and wallets | Platform in-app rules may apply to digital goods; physical goods typically use external payment |
| Cost | Lower | Higher |
| Discoverability of content | Indexable | Not indexed in the same way |
Platform capabilities and store policies change often, so verify the current state, particularly for iOS web push and installation behavior.
When a PWA fits
- You want to improve mobile web performance and reliability.
- Your audience arrives mainly from search and ads.
- You have limited budget and want one codebase.
- You need to ship and iterate quickly.
- Offline needs are modest, such as browsing recently viewed products.
When a native app fits
- You have a base of loyal, frequent customers.
- Features such as camera scanning, augmented reality, biometrics, widgets or deep device integration create value.
- Loyalty programs, in-store use or order tracking benefit from always-available access.
- Push engagement is core to your strategy, and you can measure its return.
- You have the budget and team to maintain two platforms.
Questions to answer first
- What share of revenue comes from repeat customers?
- What would the app do that the mobile site cannot?
- Do we have the capacity to support releases, bug fixes and store compliance?
- How will we drive installs? Acquisition costs for app installs can be high.
- What will we lose in SEO and sharing by moving users into an app?
Cost and maintenance
Apps require ongoing work: operating system updates, device testing, store policy changes, crash monitoring and security fixes. Budget for maintenance as a continuing cost, not only a build. PWAs share web maintenance but still need testing across browsers and care with caching bugs, which can show customers stale content.
Performance first
Whichever route you take, performance drives results. Compress images, limit scripts, use caching, test on mid-range phones and measure real-user metrics. See the Core Web Vitals article for details.
A phased path
- Optimize the responsive site.
- Add PWA enhancements where they help, such as installability and caching.
- Consider an app when you have evidence of demand from repeat customers and a clear feature advantage.
- Measure retention, order frequency and revenue per user against the web experience.
FAQ
Is a PWA cheaper than a native app?
Generally yes, since it uses one web codebase and avoids store distribution, though it still needs quality engineering.
Can a PWA send push notifications?
On many platforms, yes, but support and user flows vary by browser and operating system. Check current behavior for your audience.
Do customers prefer apps?
Frequent, loyal customers often do, but most shoppers do not install an app for a store they visit occasionally.
Will an app improve my SEO?
No. Apps are not indexed like web pages. Keep a strong website for discovery and use the app for retention.
TURN INSIGHT INTO ACTION
Let’s talk about your next step.
Share your workflow, your current systems and what you want to improve. We’ll help shape a practical way forward.
Discuss your project ↗