It usually starts the same way. A competitor launches an app, or a developer’s cold email lands in your inbox, or someone on your team says “we should really have an app.” You ask what it costs and get a number with a lot of zeros. You ask what it will do for the business and get a vague answer about “engagement.”

This is the guide to have before that conversation. It covers whether your New Zealand business needs an app at all, the cheaper options that often do the same job, what an app really costs to own, and what changed in the app stores this year that affects the maths. We build websites and apps for a living, so we’ll say plainly when the answer is “you don’t need one yet.”

Editorial 3D illustration of three glowing doors of different sizes representing a mobile website, a web app and a native phone app
There are three ways onto a customer’s phone. Only one of them is an app store listing.

First question: will anyone open it twice?

New Zealanders are online and on their phones. DataReportal’s Digital 2026: New Zealand report counts 5.06 million internet users in October 2025 (96.2% of the population) and 6.22 million mobile connections, equal to 118% of the population. Your customers can reach an app. That was never the hard part.

The hard part is getting them to keep it. Downloading is a single tap; coming back is a habit. The mobile measurement company Adjust analysed more than 5,000 apps and reported that median global retention for 2022 was 25% on day one, 9% on day 14 and 6% on day 30 (Adjust, Mobile App Trends 2023). Put simply: of every 100 people who install a typical app, about six are still using it a month later. Adjust has since published newer figures, and categories vary, but the shape has not changed. Most installs fade.

That doesn’t make apps a bad idea. It means an app needs a reason to be opened repeatedly. Ask yourself honestly:

  • Do customers use you often? A gym, a café with a loyalty scheme, a courier or a booking service gives people a reason to return weekly. A roofer or a conveyancer is used once every few years.
  • Does the phone do something the website can’t? Push reminders, offline use, scanning, location or a camera are the real reasons for a native app.
  • Is there an existing audience to hand it to? An app launched to nobody stays at zero. Your customer list, your staff and your jobs-in-progress are the audience.

If you answered “no” to all three, the money is better spent elsewhere, and you’ll find that is where most of our conversations about apps end up.

Editorial 3D illustration of a funnel where many small app icons fall in at the top and only a few reach the bottom
Installs are the top of the funnel. Repeat use is what pays for the app.

Three ways to get on your customers’ phones

“App” covers three quite different things, with very different price tags.

1. A fast, mobile-first website

Most customers meet you on their phone through a Google search or an ad, not through an app store. A website that loads quickly, reads well on a small screen and has a tap-to-call button is the baseline. If that isn’t already excellent, an app will not fix it. Our website design and build work starts here for that reason.

2. A web app

This is a website that behaves like software: customer logins, quote calculators, booking and job-status pages, staff dashboards. It runs in the browser on any phone, can be saved to the home screen, and avoids app store approval and fees entirely. For many service businesses this delivers 80% of what they imagined an app would do.

3. A native app

This is the one you download from the App Store or Google Play. It is the right choice when you need things the browser handles poorly, such as reliable offline use, deep camera or sensor access, or push notifications that people have opted into. It is also the most expensive to build and keep.

A sensible path is to start at the cheapest option that proves demand, then move up only when you can point to customers asking for more. Building the most expensive version first is the most common way to waste an app budget.

What an app really costs

We won’t give you a fixed price here, because a quote depends entirely on what the app has to do, and we’d rather scope it with you. What we can give you is the shape of it, using a published vendor guide as a reference point. HDWebsoft’s 2026 cost guide puts a simple app at $20,000 to $60,000, a mid-complexity app at $60,000 to $150,000 and a complex one at $150,000 to $500,000 or more. The guide does not state a currency and is not specific to New Zealand, and it is written by a development company, so treat it as a rough scale rather than a quote. Ask any NZ developer for an itemised price in NZD, including GST.

The build is only the visible part. The same guide says a practical maintenance budget is 15 to 20% of the initial build cost per year. Apple and Google release new operating system versions every year and your app has to keep up. Add hosting, support, analytics and the store fees below.

Editorial 3D illustration of an iceberg where the small visible tip is the app build and the large submerged part holds updates, hosting, store fees and support
The build is the tip. Updates, hosting, support and store fees sit underneath.

Questions to put to any developer before you sign:

  1. Who owns the code and the store accounts when we finish? (It should be you.)
  2. What does the first 12 months of maintenance cost, itemised?
  3. What is the smallest version that proves people want this, and what does it cost?
  4. How will we measure success, and what number would make us stop?

The news: store fees changed in 2026

If your app sells anything inside it (subscriptions, memberships, digital goods), the cut the app stores take matters. Two things to know.

Apple runs an App Store Small Business Program. Developers who earned up to US$1 million in proceeds in the prior calendar year, as well as developers new to the App Store, can qualify for a reduced commission of 15% on paid apps and in-app purchases. Most NZ businesses sit well inside that.

Google announced a restructure of Play fees on 4 March 2026. It includes a 10% service fee on recurring subscriptions, a 20% service fee on in-app purchases from new installs, a separate billing fee when you use Google Play Billing, and more freedom to use your own billing or send people to your website to pay. The rollout is staged: the EEA, UK and US by 30 June, Australia by 30 September, Korea and Japan by 31 December, and the rest of the world by 30 September 2027. New Zealand is not named in the announcement, so ask your developer which fee schedule applies to your app today. Don’t assume the headline rates apply here yet.

The practical point for a business owner: fees are a line in the budget, not a footnote. If your app takes payments, model the numbers with a developer before you commit, and remember that a web app can take payments with no store cut at all.

Animated cartoon of a man in a suit feeding banknotes into a small fire
What an unscoped app budget can feel like.

How you’ll know it’s working

An app is a business tool, so it gets judged like one. Before building, agree on three numbers with whoever builds it:

  • Active users after 30 days as a share of installs. Compare it with the 6% Adjust benchmark above. Well ahead of that is a good sign.
  • The business action the app exists for: bookings made, orders placed, repeat visits, support calls avoided. If it can’t be counted, it can’t be justified.
  • Cost per active user across the first year, including maintenance. This is the number to compare against what you spend to win a customer through Google Ads or SEO.

Then plan how people will find it. An app doesn’t market itself. Your launch needs a plan: your existing customers, your website, email, and paid search for people actively looking for what you offer. We’d set up tracking before launch so you can see which channel produces the installs that actually stick.

Where to start

If you’re weighing an app, start with a one-hour conversation about what you want customers to do and the cheapest way to get them doing it. Sometimes the answer is a native app; more often it’s a better website or a web app first. Either way you’ll leave with a clear scope and a number you can compare. See our web and app services or get in touch and we’ll talk it through.

Frequently asked questions

Does my small business need a mobile app?

Only if customers will use it repeatedly or it does something a website can’t. Most small NZ businesses are better served by a fast mobile website first, and a web app if they need logins or bookings.

How much does a mobile app cost in New Zealand?

It depends on features and platforms. Global vendor guides put simple apps in the tens of thousands and complex ones well into six figures, usually without a currency stated. Get an itemised NZD quote with GST and ongoing costs.

What’s the difference between a web app and a native app?

A web app runs in the phone’s browser and needs no download. A native app is installed from the App Store or Google Play and can use phone features like push notifications and offline storage more fully.

How much does an app cost to maintain?

One 2026 vendor guide suggests budgeting 15 to 20% of the initial build cost per year, which covers operating system updates, fixes and support.

How many people keep using an app after installing it?

Adjust’s analysis of more than 5,000 apps found median retention of 6% at day 30 for 2022. It varies by category, which is why you should plan for repeat use before building.

Do I have to pay Apple and Google a share of sales?

If you sell digital goods or subscriptions inside a native app, generally yes. Apple’s Small Business Program rate is 15% for eligible developers. Google’s fees are being restructured in stages in 2026, and New Zealand is not named in its announced rollout, so confirm current rates with your developer.

Sources

Sources checked on 12 October 2026. Vendor figures are the vendors’ own and are not NZ-specific.

Want this run for your business?

Talk to our team. We will show you where the money is leaking and what we would do about it.