A client emails, and the first line is almost always the same worry: they think they need a mobile app. What they usually mean is that the business feels serious enough to deserve one, or that a competitor just launched theirs. Neither is a reason to spend twenty thousand euros.

That word hides a decision most owners never get to make clearly, because whoever is selling the app profits from the most expensive answer. Before you commission anything, separate what a native app actually does from what you have been told it does.

The question that decides it

Here is the split that matters: does your business need customers to come back often, or does it need to be found and understood once?

A native app — the kind you download from the App Store or Google Play — is built for the first case. It lives on the phone, sends notifications, and works well when someone opens it several times a week. A food-delivery service, a gym with a class schedule, a bank: those earn the download because the customer returns constantly and the app removes friction each time.

Most small businesses are in the second case. A therapist, a law firm, a restaurant, a wellness studio — people find them, read about the service, book or call, and move on. Forcing that person to visit an app store, download an app, and create an account before they can do anything adds friction exactly where you wanted an easy enquiry.

What an app really costs in Portugal

The sticker price is only the first bill. A custom mobile app in Portugal typically runs from €4,000 to €20,000 for a simple-to-medium build, and €20,000 to €60,000+ for something with a backend, user accounts, and integrations (SETUP Tech pricing). Business apps with complex flows, multiple user profiles, and strong security requirements often land between €25,000 and €150,000+.

Then the costs nobody puts in the proposal:

Two platforms. iOS and Android are different systems. Even with a shared codebase, you maintain, test, and fix on both.
Ongoing maintenance. Reserve roughly 15% to 25% of the build cost every year just to keep it working as phones and operating systems update. An app you stop maintaining breaks within a year or two.
App store tax. Apple and Google take a commission on in-app sales, and Apple charges an annual developer fee to keep your app listed at all. Your website charges you none of that.
Discovery. A website can be found on Google the moment someone searches. An app has to be marketed into existence — people do not stumble onto it.

A €15,000 app is really €15,000, plus a few thousand every year, plus the marketing to make anyone install it — maths that only works when repeat use pays it back.

The middle option nobody mentions

Between a plain website and a full native app sits a third choice most owners are never shown: a Progressive Web App, or PWA.

A PWA is a website built so it behaves like an app. The customer can add it to their home screen with one tap, it opens full-screen with your icon, it can work offline, and it can send push notifications on Android. There is no app store, no download, no review process, and no commission on sales. It shows up in Google search like any other page.

The reason it matters is the price. A PWA in Portugal commonly costs around €1,500 to €6,000 and ships in three to six weeks, against several months and five figures for native. For a business that wants the app-like layer — an icon on the phone, offline access to a menu or schedule, a reminder notification — a PWA delivers most of it at a fraction of the cost.

It is not identical to native, and pretending otherwise would be dishonest. On iPhones, push notifications and some background features are more limited than on Android. Animations feel slightly less fluid than a true native app. If your value depends on a premium, polished feel or on hardware the browser cannot reach, those gaps are real. For most service businesses, they are invisible.

When a native app is the right call

I am not against apps — only against paying for one a website would beat. A native build earns its cost when at least one of these holds:

People use it daily or weekly, and each visit needs to be fast — a loyalty program, a booking-heavy service, an internal tool your staff live in.
You need the phone's hardware in a way the browser handles poorly: reliable background GPS, Bluetooth or NFC, the camera doing real-time work, or robust offline use.
Notifications are core to the model, and you need them to land reliably on iPhones as well as Android.
Your customers expect to find you in the app store, which is common in enterprise or regulated contexts.
The app itself is the product, not a channel to an existing business.

If none of those describe you, the app is a want, not a need — no shame in that, as long as you spend with your eyes open.

A pattern I see often

A wellness studio owner comes in convinced she needs an app for class booking and reminders, because a big fitness chain has one.

The chain's app makes sense because a member opens it four times a week; her clients book once a week at most. What she actually needs is a fast mobile site with a clean booking flow and reminders — the same job, through the website her clients already reach from Google, with no download to abandon. A PWA covers the home-screen icon if she wants it. The native build would have cost more than her whole annual marketing budget to solve a problem she did not have.

The instinct to build an app is usually a signal that the current website is doing too little — slow, hard to book on, or invisible on Google. Fix that first. If a slow site is quietly costing you enquiries, a shiny app on top just adds a second thing to maintain.

How to decide

Before you sign anything, answer these honestly:

How often will one customer use it? Daily or weekly points toward native. A few times a year points toward a website or PWA.
Does it need the phone's hardware or reliable offline use? If not, the browser can almost certainly do the job.
Are you trying to be found, or to be returned to? Found means SEO and a website. Returned to means an app might pay off.
Can you fund the build and years of upkeep after it? If the annual maintenance worries you, that is your answer.

Two products, two problems

A mobile app and a website solve different problems. One serves businesses customers return to constantly; the other serves businesses customers need to find, understand, and contact. Buy the wrong one and tens of thousands of euros go to the wrong target — the same honest-cost trap as hiring a developer versus going DIY.

If you are weighing an app, tell me what you want customers to do on their phones, and I will tell you honestly whether that needs a native app, a PWA, or just a faster website — before you spend a cent on the wrong one.

Frequently asked questions

Does my small business need a mobile app or just a website?

Most small businesses need a fast, mobile-friendly website, not a native app. A website is the right choice when customers find you through Google, read about your service, and book or contact you occasionally. A native app pays off only when customers return frequently.

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

A native app is downloaded from the App Store or Google Play and installed on the phone. A Progressive Web App (PWA) is a website that can be added to the home screen and behaves like an app — offline access, an icon, and notifications on Android — without a download or app store. A PWA typically costs €1,500 to €6,000 versus €4,000 to €60,000+ for native.

How much does a mobile app cost in Portugal?

A simple-to-medium app usually costs €4,000 to €20,000, and one with a backend, accounts, and integrations €20,000 to €60,000 or more. Budget another 15% to 25% of the build cost per year for maintenance, plus app store fees on any sales.

Can I start with a website and build an app later?

Yes, and usually that is the sensible order. Prove that mobile customers want more than your website offers, then invest in a PWA or native app once the demand is real.