Written by

WhatWillMyAppCost

We build the estimator this site runs on, and we design and build custom mobile and web software for a living. Every figure below is the estimator’s own output, except the published vendor prices, which are read off each company’s own page and dated.

You’ve heard a progressive web app can do most of what an app does without going through the App Store, and you want to know if “most” covers yours. Somebody may have told you that you need native for notifications. Or there’s a device in your product, and nobody’s said yet whether a web page can talk to it.

Below: what a PWA is and what it costs next to a native app. Then the three things a PWA does worse on an iPhone, which are Bluetooth, notifications and working with no signal, and what going native for each one costs. What a PWA can and can’t do comes from Apple’s, Google’s and MDN’s own pages.

What is a progressive web app?

A progressive web app is a website people can install on their phone and open from an icon, like an app. A native app gets built for the phone itself and installed from the App Store or Google Play.

Native here covers both ways of building one: a single codebase for both phones, which is what the estimator assumes unless you ask for two, or a separate app for each. The React Native guide goes through when two are worth it. For a customer, the first difference is installing it.

Your PWA’s icon on an iPhone
They open your site in Safari, tap the page menu button, then Share, scroll down to Add to Home Screen and tap Add. Those are Apple’s own steps, and the customer takes every one of them. Your site can’t offer to do it, because Safari doesn’t support the install prompt a site can bring up in Chrome.
Your PWA’s icon on an Android phone
Chrome keeps an install command in its menu, and your site can put its own Install button on the page.
Your native app’s icon on either phone
They search the App Store or Google Play and tap to download it.

Is a PWA cheaper than a native app?

By $2,000 on this app: $37,000 – $53,000 as a PWA against $39,000 – $55,000 native. The web app cost guide breaks the gap down.

Riders sign in, add their bike and see its service history. They find the company’s shops on a map and get a notification when a service is due or there’s a recall. Shop staff work from a web portal of their own, where they pull up a rider’s bike, log each service and send the recall notices.

What moves the number is the reason you’re looking at native. On this app, that’s Bluetooth.

Do you need a native app for Bluetooth?

If anyone using it carries an iPhone, yes. Safari doesn’t let a web page reach a Bluetooth device, so a PWA on an iPhone can’t connect to the bike at all.

Riders want to check the battery and change the assist setting from their phone. That link takes the native app to $43,000 – $63,000.

The PWA, $37,000 – $53,000
Everything but the bike. Service history, the map, the reminders and the staff portal.
The same app built native, $39,000 – $55,000
$2,000 more. Same screens, same server and same staff portal, installed from the stores.
Native, and talking to the bike, $43,000 – $63,000
Another $6,000. Finding the bike, pairing with it and asking the rider’s permission, keeping the connection up and picking it back up when it drops, and testing all of it on real bikes, since a simulator can’t stand in for one.

Going native for Bluetooth costs $8,000 on this app. $6,000 of that is the Bluetooth work, and $2,000 is the app being native.

Bluetooth doesn’t take two separate apps. For a build like this one, the estimator recommends a single codebase for both phones, with just the parts that talk to the bike written natively for each. That’s a much smaller job than two whole apps.

It also flags the one piece nobody can price yet, how well the bike’s Bluetooth protocol is written down, and adds room for it to the top of the range. A published protocol and a bike to test against keep it near the bottom of the range. Undocumented firmware can push it past the top.

Do you need a native app for push notifications?

No. A PWA can send them on Android, and on an iPhone once the customer has added it to the home screen and said yes.

They cost about the same either way. On the e-bike app, notifications add $1,500 to the PWA and $2,000 to the native app. Going native for them costs the $2,000 above and nothing else.

What native buys you here is a step your customers skip. With the native app, they download it and allow notifications. With the PWA, they add it to the home screen from Safari’s Share menu first. How many of yours will do that is a question about your customers, and the estimator can’t answer it.

Do you need a native app to work with no signal?

Not for the app to keep working. A PWA can hold pages and data on the phone and carry on with no connection. Where it falls short on an iPhone is getting that work back to the server. Safari doesn’t support the web’s version of background sync, so a PWA on an iPhone can’t count on sending saved work once it’s been closed. Chrome on Android does support it.

Working with no signal is the most expensive of the three here, more than Bluetooth, and it costs about as much in a PWA as in a native app. Going native for it costs $1,500 on this app. The offline guide prices the work itself, and explains why syncing is the expensive half.

So settle one question about the work before you pick. Does it have to reach your server without anybody opening the app again? If it does and your people carry iPhones, a PWA can’t promise that.

A PWA and a native app cost close to the same until the app needs something a web page can’t do on an iPhone. The e-bike app is $37,000 – $53,000 as a PWA and $39,000 – $55,000 native, and the Bluetooth link to the bike takes the native app to $43,000 – $63,000.

Notifications don’t need native, as long as your customers will add the PWA to their home screen. Bluetooth on an iPhone does. If work saved with no signal has to reach your server after the app’s closed, settle that before you choose.

FAQ

Questions about PWAs and native apps

Are progressive web apps still relevant in 2026?

Apple changed them in iOS 26, in September 2025. Every website someone adds to an iPhone’s home screen now opens as a web app by default, and WebKit says a site no longer has to meet any requirements for that.

What is the difference between a web app and a native app?

A native app is built for the phone and downloaded from the App Store or Google Play. A progressive web app sits between it and a plain web app: a web app people can install on their home screen straight from the browser, with no store. The web app vs mobile app guide covers the plain difference.

Can a PWA be listed in Google Play or the App Store?

In Google Play, yes, inside a small Android app that opens your PWA full screen in the phone’s browser. Google calls that a Trusted Web Activity. The App Store is different: Apple’s review guidelines ask for more than a repackaged website.

Is a PWA enough if everyone using the app has an Android phone?

It can be. As of October 2026, Chrome, Samsung Internet and Opera on Android all let a web page talk to Bluetooth devices and sync in the background, the two things Safari won’t do. Firefox supports neither. Price doesn’t decide it here: an e-bike app with a Bluetooth link to the bike is $42,000 – $61,000 as a PWA and $41,000 – $60,000 as an Android-only app.

How much does it cost to build a PWA?

$37,000 – $53,000 for an e-bike company’s app with sign-in, a map, notifications and a web portal for shop staff. A PWA is a web app, so it’s priced like one, and the web app cost guide has ranges for smaller and bigger builds.

How long does it take to build a PWA compared with a native app?

The same 14–20 weeks either way, kickoff to launch, for an e-bike app with sign-in, a map, notifications and a staff portal. Adding a Bluetooth link to the bike takes the native app to 15–21 weeks.

The calculator

Price your app as a PWA and as a native app

Describe what you want built and what it has to connect to. You get a range and a timeline, and you can switch the result to Web only to see it as a PWA.

Price my app