Web app vs website: which one does your business need?

A website shows the same pages to everyone, and its job is to tell people about your business so they call, text or book. A web app is a site people sign in to and use like a program, to book, order or check an account. It runs in the browser, so no app store is involved. A phone app is installed from the App Store or Google Play, and Apple’s rules say it has to offer more than a repackaged website.

Our advice for most small businesses is to start with a website, add a signed-in area when customers need their own information, and pay for a phone app only when you need to be in the App Store or Google Play, or need something iPhone browsers can’t do. We sell all three, including web application development, so we have a reason to steer you toward the bigger job. That’s why every rule below is quoted from Apple, Google, MDN, WebKit or the W3C with the date we read it, and every price comes from a named source. Where a point is our judgment, we say so.

Key takeaways

  • A website is the same pages for everyone. A web app adds sign-ins and does a job for each person. A phone app comes from a store.
  • An installable web app sits in between. MDN says it “can be installed on the device, can operate while offline and in the background”. On an iPhone it can send notifications from iOS 16.4, but only after the person adds it to the Home Screen and says yes.
  • Both stores turn away thin apps. Apple’s guideline 4.2 says an app that isn’t “particularly useful, unique, or ‘app-like’” doesn’t belong on the App Store, and Google Play doesn’t allow “apps that only have limited functionality and content.”
  • A website or web app pays no store fees. A phone app in both stores pays Apple $99 a year and Google Play $25 once, on top of the build.
  • The 8-question check below sorts your answers into one of four steps, from a plain website to a phone app.

Website, web app or phone app: the quick comparison

The first table is the web app vs website question itself. The second compares the two ways of putting an app on a phone. The rows are the same in both, so you can read across.

Website Web app
What it is Pages anyone can read, the same for everyone A site people sign in to and use like a program
Sign-in None Yes. Each person sees their own information
Found on Google Yes. Its public pages are the point Its signed-in pages are private. Its public pages can be found
Installed from a store No No
Works with no signal No No, unless it’s built to work offline
Notifications on iPhone No Only once it’s added to the Home Screen
Store review and fees None None
Updates Live for everyone when you publish Live for everyone when you publish
Best for Being found, then called, texted or booked Bookings, orders, accounts and records
Installable web app Phone app
What it is A web app people add to their Home Screen and open from an icon An app installed from the App Store or Google Play
Sign-in If the job needs one If the job needs one
Found on Google Its public pages can be Its store listing and your website
Installed from a store No, from the browser Yes
Works with no signal It can, if it’s built to (MDN) It can, if it’s built to
Notifications on iPhone From iOS 16.4, after it’s added to the Home Screen and the person says yes (WebKit) Yes
Store review and fees None Review before launch and for each update. Apple $99 a year, Google Play $25 once
Updates Live for everyone when you publish Each new version goes through store review
Best for Weekly visitors, and iPhone notifications without a store Being in the stores, or a phone feature browsers don’t offer

What each one is

A website

A website is a set of pages anyone can open: your services, prices, opening hours and contact details. Nobody signs in, and everyone sees the same thing. It’s the part of your business that Google can show to people searching for what you do.

A web app

A web app is a site people sign in to and use like a program. Each person sees their own information, such as their appointments, orders, invoices or files. Online banking, a booking page that remembers your past visits and a portal where clients upload documents are all web apps. It opens at a web address in any browser, on a phone or a computer, with nothing to install. A business site is often both: public pages anyone can read, and a signed-in area behind them.

A phone app

A phone app is downloaded from Apple’s App Store or Google Play and opened from an icon on the phone. Each store reviews it before it goes live, and Apple charges a yearly developer fee.

The in-between: an installable web app

MDN, Mozilla’s reference for web developers, calls this a progressive web app (PWA): “an app that’s built using web platform technologies, but that provides a user experience like that of a platform-specific app.” It’s still a web app, but people can add it to their phone’s Home Screen and open it from an icon, without a store. In the words of MDN’s progressive web apps page (last modified August 31, 2026), “Like a platform-specific app, it can be installed on the device, can operate while offline and in the background, and can integrate with the device and with other installed apps.” It does those things only if it’s built to.

Six differences that change what you pay for

Each one below is a reason to pick one option over another, with the rule behind it where there is one.

1. Sign-ins and customer data

Sign-ins are the line between a website and a web app, and in our judgment they’re where most of the extra work is. Once people have accounts, the site needs a database, a way to reset forgotten passwords, and care with what customers keep in it. A phone app with accounts needs all of that behind it too, plus the app itself.

2. Being found on Google

Google can read pages that are built with JavaScript, but it takes extra steps. Google’s JavaScript SEO basics (last updated March 4, 2026) says “Google processes JavaScript web apps in three main phases”: crawling, rendering and indexing. It adds: “Keep in mind that server-side or pre-rendering is still a great idea because it makes your website faster for users and crawlers, and not all bots can run JavaScript.” Server-side means each page is built on the server before it’s sent, and pre-rendering means it’s built ahead of time.

Pages behind a sign-in are private, so Google doesn’t see them, which is what you want for customer accounts. The pages people search for, such as your services, prices and contact details, should be plain pages built on the server or ahead of time, whatever else you build.

3. Installing it, and using it with no signal

A website and an ordinary web app need a connection. An installable web app or a phone app can keep working without one, if it’s built to, as MDN’s description above says. Ask any builder which screens will work offline, and what happens to anything a customer types while there’s no signal.

4. Notifications and other phone features

WebKit, the engine behind Safari, announced on its blog in the post Web Push for Web Apps on iOS and iPadOS (February 16, 2023): “Now with iOS and iPadOS 16.4, we are adding support for Web Push to Home Screen web apps.” That support covers Home Screen web apps only. WebKit says “A web app that has been added to the Home Screen can request permission to receive push notifications as long as that request is in response to direct user interaction,” such as tapping a subscribe button. So an iPhone customer has to take two steps before you can reach them: add the web app to the Home Screen, then say yes.

For other features, MDN keeps a record of which browsers support what. Here is what its compatibility data showed for features a business might need:

What you need Safari on iPhone Chrome on Android
Location Yes Yes
Notifications From iOS 16.4, for web apps saved to the Home Screen Yes
A number badge on the app icon From iOS 16.4, for web apps saved to the Home Screen No
Bluetooth devices No Yes, marked experimental
NFC tags No Yes, marked experimental

Source: MDN’s browser compatibility data, version 8.1.9, read November 18, 2026. Support changes over time, so check the feature again before anyone builds around it. If the job needs Bluetooth or NFC on iPhones, that points to a phone app.

5. Store rules

A website or web app goes live when you publish it. A phone app has to meet each store’s rules first.

  • Apple, guideline 4.2. In Apple’s App Review Guidelines (last updated October 16, 2026): “If your app is not particularly useful, unique, or ‘app-like,’ it doesn’t belong on the App Store.”
  • Apple, guideline 4.2.2. “Other than catalogs, apps shouldn’t primarily be marketing materials, advertisements, web clippings, content aggregators, or a collection of links.”
  • Google Play. Its Functionality, Content, and User Experience policy says “We do not allow apps that only have limited functionality and content,” and gives as an example “Apps that are static without app-specific functionalities, for example, text only or PDF file apps.”

Selling inside a phone app has rules a website doesn’t. Apple’s guideline 3.1.1 says that to unlock features or functionality within an app, such as a subscription or premium content, “you must use in-app purchase.” Physical goods, and services used outside the app such as a delivery or an appointment, go the other way: guideline 3.1.3(e) says they need “purchase methods other than in-app purchase.” For apps on the United States storefront, guideline 3.1.1(a), which covers links to other ways to pay, adds that no special permission is needed to include “buttons, external links, or other calls to action.” A website or web app takes payments without any of these store rules.

6. Updates

A change to a website or web app reaches everyone as soon as you publish it. A phone app update goes back through store review (our app cost guide gives the review times Apple and Google publish), and each customer gets it when their phone installs it.

What each one costs

We don’t publish prices. The build figures here come from our two cost guides, which name and date their sources, and the store fees come from Apple’s and Google’s own pages.

  • A website. Our guide to what a small business website costs says: “Build it yourself on Squarespace and the cheapest plan costs $228 a year. Pay someone to build a simple site that presents your business, and Small Business Trends puts it at $1,000 to $7,600.”
  • A website that takes bookings. In the same guide, Small Business Trends puts a site “that takes bookings at $3,600 to $10,000.” That’s a website with a booking feature, not a web app with customer accounts, but it’s the nearest published figure we have.
  • A web app. We found no published price for a typical small business web app with a method we’d trust. What it costs depends on what people do once they’ve signed in.
  • An installable web app. The same build questions as a web app, plus the work to make it installable and work offline. There’s no store fee.

A phone app adds two kinds of cost: the build, and the stores. Our guide to what an app costs says: “Most app projects reviewed on Clutch, a site that publishes reviews of app firms, cost $10,000 to $49,999.” For the stores, Apple’s enrollment page says “The Apple Developer Program is 99 USD per membership year,” and Google’s Play Console guide says “There is a US$25 one-time registration fee.” Then there’s the cut of digital sales: Apple’s Small Business Program offers “a reduced commission rate of 15% on paid apps and Apple In-App Purchases” to developers who qualify and enroll. The app cost guide covers Google’s cut and the yearly bills.

Can you turn your website into an app?

Yes. There are two ways, and only one of them goes through a store.

Make the site installable. This turns it into an installable web app. The W3C’s Web Application Manifest, a working draft dated November 18, 2026 that the W3C says to cite only as a work in progress, defines a file that lists a web app’s “name, links to icons, as well as the preferred URL to open when a user launches the web application.” With that file, and offline support built in as MDN describes, customers can add the site to their Home Screen and open it like an app. Nothing goes through a store.

Wrap the site in a store app. This is a phone app that mostly shows your website. Apple’s guidelines 4.2 and 4.2.2 above are the hurdle, and guideline 4.2.6 adds a warning about do-it-yourself app builders: “Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content.” On Google Play, the bar for your own site is the same limited-functionality rule. Google’s separate Spam policy has a webview rule about other people’s sites: it doesn’t allow apps whose main purpose is to “provide a webview of a website without permission from the website owner or administrator.”

In our judgment, if a wrapper adds nothing your website doesn’t already do, the installable route costs less and avoids the store rules.

Website, web app or phone app? An 8-question check

Answer each question for the job you have in mind. Each answer says which way it points and why.

Website, web app or phone app: eight questions

  1. Do people mostly read about you, then call, text or book?

    Yes: a website is your base. Every other answer adds to it.

    In the published figures above, a simple site costs far less than a typical app project.

  2. Do customers or staff need to sign in and see their own information, such as orders, appointments or files?

    Yes: add a web app, a signed-in area of your site. No: a website is enough so far.

    Sign-ins bring a database and accounts to look after.

  3. Do you need your public pages to be found on Google?

    Yes: keep them as plain pages built on the server or ahead of time, whatever else you build.

    Google calls server-side or pre-rendering "still a great idea" in its JavaScript SEO basics.

  4. Must it keep working with no signal?

    Yes: an installable web app, built to work offline, or a phone app if question 5, 6 or 7 points to one. No: a website or web app is fine.

    MDN says an installable web app "can operate while offline."

  5. Do you need to send notifications to iPhones?

    Yes, and your customers will add the web app to their Home Screen: an installable web app. Yes, but they won't take that step: a phone app.

    WebKit: from iOS 16.4, only Home Screen web apps can ask, and only after the person taps something.

  6. Does it need a phone feature, such as Bluetooth or NFC tags?

    Check that feature in MDN's compatibility data first. If Safari on iPhone doesn't support it and your customers use iPhones: a phone app. If it does, your other answers decide.

    MDN's data, read November 18, 2026: location works in Safari on iPhone. Bluetooth and NFC from a web page don't.

  7. Do people need to find you inside the App Store or Google Play?

    Yes: a phone app, and it has to do more than your website does.

    Apple's guideline 4.2, and Google Play's rule against apps with only "limited functionality and content."

  8. Will people use it every week, to book, reorder or check in?

    Yes: an installable web app, or a phone app if question 5, 6 or 7 points to one. No: a website, plus a web app if question 2 was yes.

    In our judgment, an icon on the phone is worth its extra cost only for people who come back often.

Our judgment, built on the rules quoted in this guide. Store rules and browser support change, so check the sources before you commit.

How to read your answers

Go to the furthest step that any “yes” points to. In order, the steps are a website, a website with a web app, an installable web app, and a phone app with the website still in front of it. If question 3 was yes, keep the website’s public pages built the way that answer says, whichever step you land on.

What we don’t know

  • A typical price for a small business web app. We found no published figure with a method we’d trust.
  • Whether a given app would pass review. The rules quoted here set the line, but each store decides when it reviews your app.
  • Whether browser support has changed since we read it. MDN’s data was read on November 18, 2026. We didn’t check camera access in iPhone browsers for this guide.
  • How long a website or web app takes to build. That depends on the job, and none of the sources here gives a figure. For phone apps, Clutch puts the usual timeline at “about 11 months,” as our app cost guide notes.
  • The W3C manifest’s final wording. It’s a working draft, so it can still change.

Which one to choose

For most small businesses, our answer to web app vs website is a website first, with a web app added when customers need their own information. In more detail:

  • Choose a website if people read about you and then call, text or book.
  • Add a web app if customers need their own bookings, orders or files. If only your staff will use it, at their desks, it’s closer to custom software that runs in a browser.
  • Make it an installable web app if people come back every week, if it has to work with no signal, or if you want iPhone notifications without a store and customers will add it to their Home Screen.
  • Build a phone app, alongside the website, if you need to be in the App Store or Google Play, need a phone feature iPhone browsers don’t offer, such as Bluetooth, or need iPhone notifications for customers who won’t add your web app to their Home Screen. That’s mobile app development for iPhone and Android.

Not sure which one your idea needs? Describe what people should be able to do, and we’ll tell you by phone, text or email which of these we’d build, and why.

Short answers

Is a web app just a website?

Partly. Both open in a browser at a web address. A website shows the same pages to everyone, while a web app has sign-ins and does a job for each person, such as booking an appointment or checking an order. Many business sites are both: public pages anyone can read, plus a signed-in area for customers.

Is YouTube a website or a web app?

By the definitions in this guide, it's both. Anyone can watch its public videos without signing in, which is the website part. Signed-in features, such as your own channel and your uploads, work like a web app.

Do I need an app or a website for my business?

In our judgment, start with a website if people mostly read about you and then call, text or book. Add a signed-in web app when customers need their own bookings, orders or files. A phone app makes sense when you need to be found in the App Store or Google Play, or need a phone feature iPhone browsers don't offer, and Apple's guideline 4.2 says it has to offer more than a repackaged website. The 8-question check in this guide walks through it.

Is a web app cheaper than a phone app?

We found no published price for a typical small business web app with a method we'd trust, so we can't compare the builds. What we can compare is the store costs. A web app pays none. A phone app in both stores pays Apple $99 a year and Google Play $25 once, and the stores take a cut of digital sales made through their billing. Apple's cut is 15% for developers enrolled in its Small Business Program.

What does Wico charge?

We don't publish prices, because a booking area for one shop and an app with customer accounts on both phones are different jobs. Describe what people need to do on our contact page, and we'll tell you which option we think fits before anyone talks about a price.

Sources

  1. App Review Guidelines (last updated October 16, 2026), Apple. Read .
  2. Enrollment, Apple Developer Program, Apple. Read .
  3. App Store Small Business Program, Apple. Read .
  4. Get started with Play Console, Play Console Help, Google. Read .
  5. Functionality, Content, and User Experience, Play Console Help, Google. Read .
  6. Spam, Play Console Help, Google. Read .
  7. Understand the JavaScript SEO basics, Google Search Central, last updated March 4, 2026. Read .
  8. Progressive web apps, MDN Web Docs, last modified August 31, 2026. Read .
  9. Web Push for Web Apps on iOS and iPadOS, WebKit, February 16, 2023. Read .
  10. Web Application Manifest (a working draft, dated November 18, 2026), W3C. Read .
  11. Geolocation: browser compatibility, MDN Web Docs, compatibility data version 8.1.9. Read .
  12. PushManager: browser compatibility, MDN Web Docs, compatibility data version 8.1.9. Read .
  13. Navigator.setAppBadge(): browser compatibility, MDN Web Docs, compatibility data version 8.1.9. Read .
  14. Bluetooth: browser compatibility, MDN Web Docs, compatibility data version 8.1.9. Read .
  15. NDEFReader: browser compatibility, MDN Web Docs, compatibility data version 8.1.9. Read .
  16. Website pricing, Squarespace, as cited in our website cost guide. Read .
  17. How Much Does a Website Cost?, Small Business Trends, published November 20, 2024, as cited in our website cost guide. Read .
  18. Mobile App Pricing Guide 2026, Clutch, updated September 21, 2026, as cited in our app cost guide. Read .

Your fitting, by phone

Tell us what you want made, and you’ll get a straight answer, even if that answer is “not from us”.

Book a fitting

A fitting is a first call.