When a company plans its next step online, the same question comes up: mobile website or app. In most cases the right answer is a properly built mobile website. The reason is simple: an app has to be downloaded, a website only has to be opened. Someone hearing about your company for the first time will not install anything for a one-off contact. An app starts to pay off only when the same person comes back to you regularly - a few times a month or more.
Below I take the three options apart: what makes each one distinct, what it really costs to run, and how to tell that you have outgrown a plain website.
Three options and what separates them
A mobile website (today: a responsive website) is one site that adapts its layout to screen width - it looks one way on a phone, another on a laptop. There is no separate address like m.company.com; that split disappeared years ago.
A web app is a program that runs in the browser, behind a login. It looks and behaves like an app (a dashboard, a cart, a calendar, an icon on the home screen), but it does not go through app stores. The variant with an icon and offline support is called a PWA.
A native app is a program installed from the App Store or Google Play, written separately for iOS and for Android. It has full access to the phone’s hardware and to push notifications.
| What we compare | Mobile website | Web app | Native app |
|---|---|---|---|
| How the customer gets in | link, search, QR code | link + login | download from a store |
| Visible in Google | yes | usually not (much of it behind a login) | no, only a page about it |
| Push notifications | limited | limited | full |
| Access to camera, GPS, NFC | basic | basic | full |
| Updates | instant | instant | via the store, with review |
| Cost to start | lowest | medium | highest (two platforms) |
| Cost to run | low | medium | high, ongoing |
When a website is enough (the most common scenario)
A website is enough when your goal is for someone to find you, check you out and get in touch. That covers local services, construction firms, clinics, law offices, manufacturers, restaurants and most retail. The customer searches on Google, clicks, looks at the offer, calls or sends a form - and that is where their journey ends. An app in this scenario only adds a barrier.
Test yourself with a simple question: how many times a year does the same person need to deal with my company? Once or twice - stay with a website. A dozen times or more, and with a login to their own data - it is worth doing the maths on an app.
If you are just starting out, the usual starting point is a brochure website for a small business, and for a single specific service or campaign - a landing page. Both are mobile by definition, because phone traffic dominates in practically every industry today.
When a web app makes sense
A web app makes sense when the customer has their own account and their own data with you: order history, individual pricing, documents, bookings, stock levels. That is the most common point at which a company genuinely outgrows a plain website - and it usually happens in B2B.
Typical signals:
- Sales reps retype orders from emails and phone calls into the system by hand
- Every trade customer has a different price list and different discounts, and you send them as PDFs
- Customers email you asking about order status or product availability
- Someone in the company exports the same file from the ERP every single day
- Wholesale orders go through a spreadsheet circulating as an attachment
In situations like these you build a B2B order panel for trade customers or a full B2B platform wired into the warehouse system. It runs in the browser, so the trade customer installs nothing and you can ship fixes the same day. For most companies this is exactly the “app” they were asking about - just without an app store behind it.
When you genuinely need a native app
A native app is justified when you need something a browser cannot do - or does badly. It is a short list:
- Push notifications the business model depends on (couriers, on-call teams, service alerts)
- Offline fieldwork - inspection reports, handovers, stocktakes with no signal
- Phone hardware - barcode scanning all day, NFC, Bluetooth, continuous GPS
- Daily, multi-minute work by the same people in one tool
- In-app payments and subscriptions settled through the stores
If none of those describes your situation, a native app will be a more expensive version of what you already have. On top of that come the things that are easy to forget at the idea stage: developer accounts with Apple and Google (paid, annual or one-off - rates get changed, check at the source), a review process for every release, forced updates after OS changes, and the fact that users sit on old versions for months.
Mobile website or app - three questions that settle it
When a decision has to happen fast, I ask three questions.
Does the customer have their own account and their own data with you? If not, you need a website, not an app. A brochure site, a service page or a shop handles the whole path: being found, being checked, being contacted. I build websites for companies for exactly that scenario, and that is where most conversations that started as an app idea end up.
Do you need something a browser cannot do? If not, a mobile app made out of your website is built today as a PWA: the same site added to the phone’s home screen, with an icon and basic offline support. No store, no review of every release, no second product to maintain. The App Store and Google Play only make sense when you genuinely need push, phone hardware or a store listing as a sales argument.
Can you carry the upkeep of two things at once? This is where the “web app or mobile app” question is settled by money. The customer sees roughly the same thing either way: a screen, a login, their own data. The company pays very differently - a web app is one codebase and a fix shipped the same day, a native app is two platforms, two release cycles and support for old versions dragging on for years. If there is no standing budget for that, the choice has already been made.
Three answers of “no” mean you need a website that loads fast on a phone and leads to contact, not an app.
What it costs - to start and to run
Below are realistic brackets for a company in Poland. I state the prices for my own projects outright; treat the rest as an order of magnitude, because vendor price lists change every year.
| Option | Start | What comes later |
|---|---|---|
| Company website / store (my fixed bid) | usually 5,000-10,000 PLN net (Polish market rates) | hosting, domain, maintenance |
| Web app, customer panel, B2B | quoted individually after analysis | server, integrations, development |
| Native app on two platforms | the most expensive option, a multiple of a website | store accounts, releases, version support |
| Technical maintenance with me | - | Basic from 1,000 / Pro from 2,000 / Premium from 3,500 PLN net per month |
The most commonly ignored cost is not the build, it is life after launch. A website left unattended degrades slowly; a native app degrades fast and hard - after an OS version change it can simply stop launching. If you want to compare the brackets for websites alone, I laid them out in the piece on what a website costs.
The app landing page - the item that falls out of the budget
If you are building an app, you still need a website. Nobody arrives at an app store out of thin air: a person first reads about the solution on Google, on LinkedIn or from an ad, and only then taps “download”. The app’s landing page is the only place that gets indexed by search engines, so without it your app is invisible outside the store.
A good app landing page has five things: one sentence saying what it does and who it is for, screenshots of the real product, an answer to “is this safe”, buttons to both stores that detect the user’s OS, and a pricing section. The rest is decoration.
How to check whether your website is genuinely mobile
Before you spend money on an app, run a quick test on your own phone, on mobile data, not on office Wi-Fi:
- Open the homepage and count how many seconds you wait for the first content
- Check whether you can tap the phone number and whether it dials straight away
- Fill in your own contact form all the way through and see whether the email arrives
- Open the longest subpage and scroll it - does anything spill sideways
- Increase the text size in your phone settings and check whether the layout falls apart
If any of those goes badly, you have your answer: the problem is not the lack of an app, it is a website that is not doing its job. Fixing those things costs many times less than building anything from scratch, and you can check mobile load speed yourself - I described it in the mini speed audit.
The most common mistake: an app instead of fixing the website
I see this scenario regularly. A company has a site from years ago that loads slowly and does not sell, so the decision comes down: “let us build an app”. Six months later the app exists, it has a few dozen downloads, and customers still land on the same old website - because that is what shows up in Google. The result: two products to maintain and no change in the number of enquiries.
The order that works: first the website has to be fast, readable on a phone and have a clear contact path. Only when that is standing and you can see returning users do you add a panel or an app. While you are at it: since June 2025 the EU digital accessibility requirements apply to some companies and services - so if your site needs a refresh and optimisation anyway, it is worth doing both in one pass.
How to settle this without guessing
I start with a free diagnosis: I look at your site, at how mobile users behave on it, and at the process you want to improve. Out of that comes one recommendation rather than three options - either “we fix the website and that is enough” or “you genuinely need a panel here”. For larger work you get a written quote with scope and deadline before anything starts. If the diagnosis says “stay with the website”, I say so outright, even when it means a smaller job for me.
Frequently asked questions
Is a mobile website the same as a responsive one?
In practice, yes. It used to be a separate version at m.company.com; today one responsive site adapts to any screen. A separate mobile version is outdated and doubles the maintenance cost.
Will an app help me rank higher in Google? No. Search engines index websites, not apps from stores. If visibility matters to you, the money works harder in the site and its content than in an app - and the app needs a website to talk about it anyway.
How long does it take to build a business app? A simple customer panel in the browser is usually a few weeks; a native app on two platforms takes months, plus time for store review. The timeline depends mainly on integrations with systems you already have, which is why I give it only after the scope is agreed.
Is a PWA enough instead of an app from the store? Very often, yes. A PWA can be added to the phone’s home screen, works offline within basic limits and updates itself, with no stores involved. It falls short when you need strong push notifications, full hardware access, or presence in the App Store as a selling point.
Need something like this on your side? I design and build websites for B2B companies - from scratch or as a rebuild of what already stands. Send me the scope and a quote with a date comes back.