“We need an app now too” is a sentence we hear more and more often in consultations with small businesses, practices and service providers from the region – usually triggered by a competitor that has one, or by customers asking for online appointment booking. The honest answer is almost never a simple yes or no, but rather: it depends on what you want to achieve – and whether an “app” in the everyday sense really has to be a native app, or whether another technical solution achieves the same goal more cheaply and quickly.
This guide sorts out the terms, shows typical use cases for small businesses, gives realistic cost ranges and offers honest guidance on when your own app really pays off – and when a much cheaper alternative serves the same purpose.
App, PWA or website with features – what's the difference?
A native app is an application developed specifically for iOS and/or Android, published in the respective app store and downloaded from there. It has full access to device functions such as the camera, push notifications or GPS and also runs without an internet connection if designed accordingly. The price: higher development effort, usually two separate development paths for iOS and Android (or a cross-platform framework as a compromise), plus ongoing maintenance due to app store requirements and operating system updates.
A progressive web app (PWA) is essentially a website that behaves like an app: it can be placed as an icon on the smartphone home screen, partly works offline and can send push notifications to a limited extent – without going through an app store. For many small businesses, a PWA is the most pragmatic middle way: considerably cheaper than a native app, but functionally closer to a “real” app than a classic website.
A website with features means a well-built, responsive website with built-in tools – for example an appointment booking system, a customer login or a form assistant like our own service request system. For many use cases in the trades and service sector, this is the fastest and cheapest solution and works immediately on any device without installation.
Typical use cases of small businesses – and the right solution for each
Online appointment booking (practices, hairdressers, service providers): in most cases a well-integrated booking function on the website is entirely sufficient – a native app rarely adds real value here, since customers seldom install an app just to book an appointment.
Digital job or service management (trades businesses): an internal web application for staff in the field is often worthwhile here – accessible via the browser on the smartphone, without every employee having to download an app from the store. Our own service request system for customer orders works on exactly this principle.
Customer portal with access to documents or invoices (tax advisers, law firms, B2B service providers): a password-protected web portal usually serves the same purpose as an app here, without the hurdle of a download for occasional users.
Loyalty with push notifications (e.g. offers, reminders, news): this is where a real app, or at least a PWA, shows its strongest advantage – push messages reach customers directly, without them having to actively visit a website.
Vehicle or site tracking with camera and GPS (trades, logistics, field service): when deep access to device functions such as camera, GPS or offline use without network coverage is needed, the route usually does lead to a native app or at least a powerful PWA.
What does your own app realistically cost?
Quoting flat prices for “an app” would be dubious – the effort depends heavily on the range of functions. As a rough guide, here is what influences the price most in practice:
Range of functions. A simple app with static content and a contact form is considerably cheaper than an app with a login system, payment processing, appointment management and push notifications.
Number of platforms. A PWA or a cross-platform app (one code base, runs on iOS and Android) is cheaper than two completely separate native apps for iOS and Android.
Connection to existing systems. If the app has to communicate with an existing customer database, inventory system or accounting software, the development effort rises noticeably compared with a standalone solution.
Design effort. An individually designed, well-thought-out user experience takes more development time than a functional but simple interface – although for small businesses in particular, a simple, clear design is often the better choice than unnecessary complexity.
Don't forget the running costs. Besides the one-off development, native apps usually involve annual developer account fees with Apple and Google, plus effort for maintenance, security updates and adjustments to new operating system versions – an app is rarely “finished” on publication but requires continuous care.
Our recommendation: before any decision, get a concrete quote tailored to your use case rather than relying on flat prices from the internet, which rarely reflect your actual range of functions.
Alternatives to your own app – and when they're enough
Before investing in an app, it's worth taking an honest look at existing alternatives: a well-built, responsive website with the required functions built in reaches the same users on every smartphone as an app – without the download hurdle, which experience shows a considerable proportion of potential users shy away from. Existing appointment booking or CRM tools can often be integrated directly into your website without the need for a complete in-house development. A PWA combines most of the advantages of an app (icon on the home screen, partial offline use) with the lower costs and easier maintenance of a website.
In our experience, one of these alternatives is entirely sufficient for a considerable proportion of small businesses – “our own app” is often more of a status symbol than an actual business necessity. We tell you that honestly in the consultation, even when it means less development work for us.
When your own app really pays off
A native app, or at least a powerful PWA, generally pays off when at least one of these conditions applies: your customers or staff use the application very frequently (several times a week or daily) – with infrequent use, the download hurdle outweighs the gain in convenience. You need genuine offline access, for example on construction sites without reliable coverage. Push notifications are a central part of your business model, for example for time-critical reminders or offers. You make intensive use of device functions such as camera, GPS or sensors that can only be used to a limited extent via a website. An internal staff application rather than a customer app: for internal tools that your own staff use daily in the field, the download hurdle isn't an issue anyway, so an app solution pays off more often here than for customer-facing applications.
Discoverability: why a website often brings more new customers than an app
A point that is often lost in app discussions: a native app has to be actively found and downloaded in the app store – users rarely search there specifically for a local trades business or practice unless they already know the name. A website, on the other hand, is found through Google searches such as “electrician Vaihingen an der Enz” or “physiotherapy near Stuttgart” by potential new customers who have never heard of your business before. For winning new customers, a well-findable, locally optimised website is generally more effective than an app – the app is better suited to retaining existing customers, not to winning new ones.
This distinction is worth making when setting priorities: if the main goal is to reach new customers in the first place, invest in a good, locally findable website first. Only once there is a stable, recurring customer base that would actually benefit from an app does investing in your own app make economic sense.
Common mistakes in small businesses' app projects
Too many features at once. The wish to cover everything straight away – booking, payment, chat, reviews, loyalty points – drives up costs and development time unnecessarily. A lean first version that is extended later is the smarter strategy in almost every case.
No clear definition of the target group. Building an app “for all customers” without knowing how many of them would even be willing to download an app often leads to disappointing user numbers after launch. A short survey of existing customers before the project starts brings clarity here.
Forgetting maintenance from the outset. Many projects only budget for development costs, not for ongoing care – with the result that the app no longer works properly after one or two operating system updates and gathers dust, unused, in the stores.
No test run before the full rollout. Publishing an app directly to your entire customer base without first letting a small group test it often means that avoidable errors only come to light after launch – with correspondingly more effort to fix them.
Our development process
If, after honest advice, it turns out that an app or PWA really is the right solution, we proceed in a structured way: needs analysis, in which we jointly clarify which concrete problem the app should solve – not “we need an app”, but “our customers should be able to book an appointment online without calling”. Technology decision, in which we tell you honestly whether a native app, a cross-platform solution or a PWA is the most economical choice for your use case. Design and development with a React/TypeScript stack for web and PWA solutions, agreed in manageable stages so that you can see and steer progress continuously. Test phase before publication, including a real-world test by you or selected customers. Publication and handover, including a short introduction so that you and your team can use the application independently.
Don't forget maintenance
An app – whether native or a PWA – is not “finished” on publication. Operating system updates from Apple and Google can affect existing functions, security holes must be closed promptly, and new requirements can arise as the number of users grows. So budget for ongoing maintenance from the outset rather than leaving the application to its own devices after publication – an unmaintained app becomes less reliable over time and, in the worst case, a security risk.
Frequently asked questions
Do I really need a native app to start with, or is a website with features enough? In most cases, a well-built website with the necessary functions is entirely sufficient to start with. An app usually only pays off when there is a concrete, frequently recurring use case that a website can't cover.
How long does it take to develop an app? That depends heavily on the range of functions – from a few weeks for a simple PWA to several months for an extensive native app connected to existing systems. After the needs analysis we give you a realistic time frame.
Can I switch from a PWA to a native app later? Yes, that's possible in many cases and even a sensible path: with a PWA you can test more cheaply whether usage actually reaches the expected volume before investing in a more elaborate native app.
What does publishing in the app store cost? Apple charges an annual developer account fee, Google a one-off registration fee for the Play Store account. These costs are manageable but shouldn't be forgotten in the overall calculation.
Do I have to take care of maintenance myself? No, we can take this over as part of a maintenance package – including security updates and adjustments to new operating system versions, so that you can concentrate on your core business.
Is an app also worthwhile for a very small business with just a few employees? That depends heavily on the specific use case – for internal field service tools it can pay off even with a small number of staff; for a pure customer app with a very small customer base, a website is usually the more economical choice.
Does an app bring more new customers than a good website? As a rule, no – for winning new customers via Google search, a locally optimised website is usually more effective. An app shows its value mainly in retaining existing customers.
Can you extend an existing app later instead of rebuilding it completely? Yes, that's the norm. We deliberately design projects so that individual functions can be added later without having to redevelop the entire application.
Conclusion
“We need an app” is rarely the right starting question – the better question is: “Which concrete problem should be solved digitally, and which technology solves it most cheaply and reliably?” For many small businesses, a well-built website or PWA is entirely sufficient; for others – especially with intensive daily use or a genuine need for offline access – investing in a native app really does pay off.
Are you wondering whether an app or another digital solution would be worthwhile for your business? Let's clarify together, in a no-obligation conversation, what really makes sense for your specific use case.
Contact: +49 7042 16391 · [email protected] · Grabenstraße 18, 71665 Vaihingen an der Enz, Germany (near Stuttgart). We are happy to help in English.



