The short answer
Most small businesses should build a web app or progressive web app first: it costs less than a native mobile app, works on every device, and does not require App Store approval or a separate codebase. On Pythn's published pricing, full web apps start from $15,000 and cross-platform mobile apps from $25,000 — and if the office also needs a web admin panel, the mobile app adds to the web build rather than replacing it.
Native earns its keep in four situations: long stretches without signal on iPhones, Bluetooth or NFC hardware, customer notifications as the core of the product, or a store listing your business genuinely needs. Otherwise, start on the web. A PWA covers the middle ground: it installs to the home screen, keeps working when the signal drops, and can send push notifications — on iPhones, once someone has added it to the Home Screen.
The decision matrix: five questions that pick the winner
Answer these in order. No reason to go native by the end? Build a web app — a PWA if people will use it often.
1. Who uses it, and how often?
A customer who pays an invoice twice a year shouldn't have to install anything; send them a link. Staff using a tool daily can be set up once, so a PWA or a native app are both in play.
2. Does it have to work without signal?
A few minutes in a dead zone is PWA territory. Hours without signal on iPhones, with photos and signatures piling up, points to native, for the reasons below.
3. Does it need hardware beyond the camera and GPS?
Photos and location have worked in browsers for years. Bluetooth printers, sensors, and NFC tags are where web apps run out of road, especially on iPhones.
4. How much do notifications matter?
If notifications are a useful extra, a PWA sends them. If they are the product, and your customers are iPhone users, native is the safer bet.
5. Do you need to be in the app stores?
Some do: customers search the store for you by name, or a partner expects a listing. If nobody will look for you there, skipping the stores saves the accounts, the review step, and the payment rules.
What each option costs, with real numbers
These are Pythn's published prices, not an industry survey.
- Web app: full web apps start from $15,000 on our Web & Mobile App Development page, and most business platforms — authentication, admin controls, a real data model, integrations — land in the $15,000–$50,000 band.
- PWA: no separate price line — a PWA is the same web app plus a manifest and, for offline use, a service worker. Offline work is scope like any other: the more of it, the more it costs.
- Cross-platform mobile app: from $25,000 depending on features, built once for iOS and Android with React Native or Flutter. That's a second codebase beside your website, with store review on every release.
Two things widen that gap. A mobile app often sits on top of a web app — a common pattern is an office in a web admin panel while field staff use the phone — so the real choice is web alone, or web plus mobile. And maintenance follows the build, at our planning rule of 15–20% of build cost per year (see the maintenance cost guide): $15,000 of web plus $25,000 of app runs $6,000–$8,000 a year, against $2,250–$3,000 for the web app alone.
Then the stores. The Apple Developer Program is $99 per membership year; Google Play charges a one-time $25 registration fee. Both ask companies for a free D-U-N-S number from Dun & Bradstreet (Apple's rule, Google's), and Google makes personal accounts created after November 13, 2023 run a closed test with at least 12 testers for 14 days before applying for production access. Keep the accounts in your company's name — one of the questions to ask before hiring a developer.
Commissions depend on what you sell. For physical goods or services — a repair visit, a delivery, a booked appointment — Apple's App Review Guidelines (3.1.3(e)) require a payment method other than in-app purchase, and Google's Payments policy says Play's billing system must not be used. They apply when you charge for the app or sell digital features inside it: Apple's Small Business Program rate is 15% for qualifying developers, those new to the App Store or with up to $1 million in proceeds the prior calendar year. Google Play's service fees for US users changed on June 30, 2026, turning on the purchase type, install date, and programs you join.
When native mobile actually wins
Browsers now do much of what used to need an app store: web push has been available across browsers since March 2023. Four gaps remain.
Long stretches offline, on iPhones
A PWA can work offline: service workers are intended, in MDN's words, “among other things, to enable the creation of effective offline experiences.” The catch is what happens when the signal returns. The Background Synchronization API sends requests that couldn't go out while the app was in use, and per MDN's compatibility table Safari doesn't support it, so on an iPhone the dependable moment to upload is the next time someone opens the app in coverage. A native iOS app hands the upload to the system, which Apple says can continue even when the app is suspended or terminated.
Take a heating and cooling contractor whose technicians capture photos, parts, and signatures in basements and rural dead zones. On company Android phones, a PWA in Chrome syncs that work in the background; if the crew carries iPhones and a stuck signature means an unbilled job, build native — our HVAC and field-service page lists what goes into those apps.
Bluetooth, NFC, and other hardware
Camera and location are fine: MDN lists camera access as available across browsers since September 2017 and the Geolocation API since July 2015. Bluetooth and NFC are not — neither Web Bluetooth nor Web NFC works in Safari. To print to a Bluetooth label printer or tap NFC tags on iPhones, go native, where Apple's Core Bluetooth and Core NFC frameworks do exactly that.
Notifications on iPhones
Apple supports web push for Home Screen web apps on iOS and iPadOS 16.4 or later, and the app can ask permission only in response to a direct action, like tapping a subscribe button. For staff, that's a one-time setup. If reminders to customers are the whole point, don't make them depend on it: use a native app, or send text messages and email.
Being in the store
If customers will search the stores for you, you need a listing — and on iOS, a real app: guideline 4.2 expects “features, content, and UI that elevate it beyond a repackaged website.” On Android, a PWA can be packaged with Trusted Web Activity and uploaded to the Play Store. Budget for review: Apple reviews 90% of submissions in less than 24 hours on average, while Google says some accounts see up to seven days or longer. A fix to a web app ships when you deploy it.
PWAs up close: what they are and when they beat both
Google's web.dev defines PWAs as web apps “built and enhanced with modern APIs to provide enhanced capabilities while still reaching any web user on any device with a single codebase.” Concretely: your web app, plus a manifest that tells the device how to install it, plus usually a service worker for offline caching and push.
- Android: Chrome can offer to install a PWA once it meets Google's installability criteria — HTTPS, a manifest with a name, icons, a start URL and an app-style display mode, and a visitor who has tapped the page and spent 30 seconds on it. Per MDN, Chrome on phones with Google Mobile Services and Samsung Internet on Samsung devices install it as a real app, with its own entry in the launcher and settings.
- iPhone and iPad: Safari doesn't support the install-prompt event a site uses to offer its own Install button, so people add the app from the Share menu, which since iOS 16.4 works in Safari, Chrome, Edge, Firefox, and Orion. Safari 26, for iOS 26 and iPadOS 26, added support for any website to become a web app.
A PWA usually wins for staff tools used daily, portals with repeat customers, and field work with brief gaps in signal: set it up once per phone, updates ship when you deploy, and cached forms keep working when the signal doesn't.
How Pythn approaches the choice
Make the call before the build starts, while changing it means editing a document rather than rewriting code. Pythn's five-stage process opens with a free discovery call (here's what happens in one) and produces a written design document — screens, data model, integrations — with fixed scope and fixed price before any code is written.
Either way, you own the code and the deployment, and 30 days of post-launch support are included. If it's web now and mobile later, build the backend as a documented API from the start — what our API & Backend Development work delivers.
Frequently asked questions
Do I need a mobile app or is a website enough?
For most small businesses, a website or web app is enough to start. You need a native app for long stretches without signal on iPhones, Bluetooth or NFC hardware, customer notifications as the core feature, or a store listing. Otherwise a responsive web app, installable as a PWA, does the job for less — our five-question cost calculator shows which band it lands in.
What is a progressive web app?
A progressive web app is a web app that can be installed and used like an app: it opens from its own icon, works offline, and can send push notifications. Google describes PWAs as web apps that reach “any web user on any device with a single codebase.” On Android, Chrome can offer to install one; on iPhone and iPad, people add it from the Share menu.
Can a PWA send push notifications to iPhones?
Yes, with conditions. Apple supports web push for Home Screen web apps on iOS and iPadOS 16.4 or later, so someone has to add the app to their Home Screen first, and the app can ask permission only in response to a direct action such as tapping a subscribe button. On Android, Chrome supports web push with no install at all.
How much does it cost to put an app in the App Store and Google Play?
The accounts are the cheap part: $99 per membership year for Apple and a one-time $25 registration fee for Google Play. The real cost is the app — from $25,000 for a cross-platform build on Pythn's pricing, plus 15–20% of build cost a year to maintain it — and, if you sell digital features inside it, the store's commission.
Can we start with a web app and add a native app later?
Yes, and it's often the cheaper path. Build the backend as a documented API from day one, and a mobile app added later talks to the same data instead of duplicating it. You also learn which features really need to be native before paying for them. Our guide to custom software timelines covers why a smaller first scope ships sooner.