Every few months, a business owner asks us some version of: "should we build an app?" It is a fair question — apps feel like growth. They sit on the home screen, they send push notifications, the big brands all have one. But an iOS app is also one of the most expensive marketing decisions a business can make, and for many companies a good mobile website would do the job better for a tenth of the cost. This guide gives you the honest maths.

When an iOS app genuinely pays off

Apps earn their keep in specific situations. If several of these describe your business, an app is worth serious consideration:

  • Repeat usage: Your customers come back weekly or more — ordering food, booking classes, tracking workouts, managing an account. Apps win on repeat visits because they remove friction: one tap versus open browser, type URL, log in. If customers use you once a year, an app will sit unopened and eventually get deleted.
  • You need the phone's capabilities: Camera, GPS in the background, push notifications, offline access, Apple Pay, biometric login, Bluetooth. If your service genuinely needs these, a website cannot fully substitute. If it does not, you are paying for capabilities you will not use.
  • Retention is the business model: Subscriptions, loyalty programmes, marketplaces — businesses where keeping the customer matters more than finding them. Push notifications and home-screen presence are retention tools, and they work.
  • Your audience is iOS-heavy: In the UK, iPhone ownership skews towards higher-income demographics. If your customers are predominantly iOS users — common in finance, premium retail and professional services — you can sometimes launch iOS-only and reach most of your market.
  • App Store presence is marketing: Being in the App Store puts you in front of people searching for solutions. For some categories, the store listing itself is a meaningful acquisition channel.

The common thread: the app has to earn its place on the home screen by being used regularly or doing something a website cannot. "Our competitors have an app" is not a strategy.

When a mobile website is enough

Be honest about this list, because it describes most businesses:

  • Infrequent use: If customers interact with you a few times a year — estate agents, solicitors, car dealerships — nobody will keep your app installed. A fast, well-designed mobile website serves them better.
  • Content and discovery: If your goal is to be found on Google, an app actively hurts you — app content is largely invisible to search engines. Blogs, service pages and local SEO live on the web.
  • Simple transactions: Booking a table, requesting a quote, buying a product — all work beautifully in a mobile browser now, including Apple Pay on the web. An app adds download friction to a process that should have none.
  • Limited budget: An app needs building, then maintaining, then updating for every iOS release, then marketing so anyone downloads it. If the budget is tight, every pound is better spent on the website and on getting found.

A useful test: would your customers miss the app if it disappeared tomorrow? If the honest answer is no, build the website.

The honest maths

Let us talk numbers, because this is where app dreams usually meet reality:

  • Build cost: A genuinely useful native iOS app — designed properly, built properly, tested properly — typically starts around £25,000–£50,000 for something focused, and climbs well into six figures for anything complex (marketplaces, social features, heavy integrations). Anyone quoting £5,000 for "an app" is quoting a template you will outgrow or regret.
  • Ongoing cost: Budget 15–25% of the build cost per year for maintenance: iOS updates, bug fixes, small improvements, backend hosting. An app is not a one-off purchase; it is a commitment.
  • Acquisition cost: Building it is half the battle. Getting downloads costs money — App Store optimisation, paid acquisition, or driving your existing audience to install it. Many businesses build the app and then discover nobody downloads it, because "we have an app" is not a marketing plan.
  • The retention cliff: Industry data is sobering: most apps lose the majority of users within the first month, and a large share are deleted. Your app needs a reason to survive the first week on someone's phone. Push notification strategy, onboarding and genuine utility are not optional extras.

The break-even question to ask: how many customers, retained how much longer or spending how much more, does the app need to deliver to pay back build plus three years of maintenance plus acquisition? Write the number down. If it looks heroic, it probably is.

Native iOS vs cross-platform

You have probably heard you can build once and run on both iPhone and Android. Cross-platform frameworks (Flutter, React Native) are mature and sensible for most business apps — one codebase, one team, both stores. The trade-offs:

  • Go native iOS (Swift) when: You need deep integration with Apple-specific features, maximum performance (games, AR, heavy media), or your audience is overwhelmingly iOS and you want the most polished possible experience.
  • Go cross-platform when: You need both iOS and Android (most businesses do eventually), budget matters, and your app is a standard business app — forms, lists, payments, notifications, maps. Modern cross-platform apps are indistinguishable from native for these use cases.
  • Do not go: Cheap template app-builders for anything you intend to grow. They are fine for a prototype; they become a rewrite the moment you need anything custom.

Note the App Store review process applies regardless: Apple reviews every app before publication, and rejections for guideline issues (privacy disclosures, login requirements, placeholder content) are common on first submission. Budget time for it — and build to the guidelines from the start rather than fixing rejections afterwards.

Making the decision: a practical framework

Work through these questions in order:

  1. Frequency: Will customers use this weekly or more? No → website.
  2. Capability: Does it need phone features a website cannot provide? No → website.
  3. Economics: Does the retention or revenue uplift plausibly cover build + 3 years maintenance + acquisition? No → website.
  4. Distribution: How will people discover and download it? "Our website will mention it" is not a plan. No plan → do not build yet.
  5. Commitment: Are you prepared to maintain and improve it for years? No → website.

If you pass all five, an app is a genuine growth investment. If you fail any, fix that thing first — usually it means investing in the mobile website and in being found, which pays off whether or not you ever build an app.

For the earlier stages of the journey, our guide on taking an app idea to launch walks through validation, scoping and what to build first.

And if the framework points to "build", our custom mobile app development team will scope it honestly — including telling you when the answer should have been a website.

FAQs

How much does an iOS app cost in the UK?

A focused, well-built native or cross-platform business app typically starts at £25,000–£50,000; complex apps run into six figures. Then budget 15–25% of build cost annually for maintenance, plus the cost of getting people to download it. Be wary of quotes far below this range — they usually mean templates, offshore corners cut, or a scope far smaller than you imagine.

Should we launch iOS-only or iOS and Android?

It depends on your audience. UK iPhone share is high but Android still holds roughly half the market — launching iOS-only means ignoring half your potential users. Cross-platform development has made dual launch much more affordable than it used to be. iOS-only makes sense when your data shows your customers are overwhelmingly on iPhone.

How long does it take to build an app?

A focused v1 typically takes 3–6 months from approved designs to App Store approval. Complex apps take longer. Add time for App Store review (usually days, but rejections happen) and — critically — do not plan your launch marketing around the earliest possible date. Something always slips.

Can a website really do what an app does?

For many business use cases, yes: modern mobile websites handle payments (including Apple Pay), bookings, accounts, notifications (web push, with limits) and offline access (partially). What websites cannot do: live on the home screen with full push notification power, access some device features deeply, or work fully offline. Match the technology to what you actually need.

What is the biggest reason business apps fail?

Nobody downloads them — or everyone deletes them within a month. The failure is rarely technical; it is a distribution and retention failure. An app without a download strategy and a retention strategy is an expensive icon. Before you commission a build, talk to us and we will stress-test the business case with you, even if the conclusion is "not yet".

Web Development Visuosofts Get a Quote