App Store Optimization is the work of improving how your app gets found and how well its store page converts, and it matters because in New Zealand 95% of people aged 15+ use the internet, 89% own a smartphone, and 65% of App Store downloads follow a search. If you're asking what is app store optimization, the short answer is this: it's part search strategy, part product marketing, and part conversion work inside the app stores.
You launch the app. The team's tired but buzzing. You've shipped something real, maybe after months of bug fixes, pricing debates, and far too many Slack threads about button colours. Then the listing goes live and… not much happens.
That silence catches a lot of founders off guard. They assume a solid product will carry itself. Sometimes it does, for a moment. Usually it doesn't. App Store Optimization, or ASO, is the art and science of getting discovered in a crowded marketplace, then giving people enough confidence to tap install instead of scrolling past.
Most launch problems aren't product problems at first. They're discovery problems.
Your app can be useful, polished, and better than what's already out there, but if people can't find it in the Apple App Store or Google Play, it may as well be sitting in a locked cupboard. ASO fixes that. It helps the stores understand what your app does, and it helps humans decide whether your app looks worth their time.
The easiest way to explain what is app store optimization is to compare it with SEO. SEO helps a website show up in Google. ASO helps an app show up inside app stores.
That sounds simple, but the stakes are a bit different. In web search, you're often trying to win a click. In app stores, you need to win a search result, then a store-page visit, then an install. It's a tighter funnel, and every small detail counts.
Practical rule: ASO is not gaming the algorithm. It's making your app understandable, relevant, and convincing.
A founder who's planning a release should treat the app listing like part of the product launch itself, not an afterthought. If you want a useful companion resource, this checklist of steps for launching a product is a sensible reminder that launch readiness includes positioning, messaging, and distribution, not only shipping code.
Teams often stumble due to their approach. They treat the app title, screenshots, and description like boxes to fill in before pressing publish. That's the wrong mental model.
Your listing is your first pitch. For many users, it's your only pitch.
A few things matter immediately:
If your product is still in build mode, it also helps to understand how the app itself is being shaped before the listing goes live. This guide to mobile app development in New Zealand gives useful local context on that side of the equation.
NZ and AU founders sometimes treat ASO like a nice extra for later, something to tidy up after paid acquisition starts. I think that's backwards. In our corner of the market, ASO should sit close to the top of the pile.
The reason is blunt. The audience is already on mobile, already connected, and already searching.
According to Business of Apps research on app store optimization statistics, 95% of people aged 15+ in New Zealand use the internet, 89% own a smartphone, and Apple reported 65% of App Store downloads follow a keyword search. That's not a fringe channel. That's the front door.
If you opened a café on a busy Wellington or Melbourne street, you wouldn't hide the sign, frost the windows, and hope people wandered in by instinct. Yet that's basically what founders do when they launch with weak ASO.
Search-driven discovery matters because users often arrive with intent. They're not browsing aimlessly. They want a budgeting app, a booking tool, a meditation app, a field service tracker, a kids' learning app. If your metadata and creative don't signal relevance fast, you miss that moment.
That's also why ASO isn't just about ranking. It's about matching intent.
A lot of teams in NZ and AU operate with sensible budgets, not Silicon Valley fantasy money. That makes efficiency matter more.
You can run Apple Ads, Google App Campaigns, Meta, TikTok, influencer pushes, all of it. But if the store listing is weak, you're pouring paid traffic into a leaky bucket. Founders feel this quickly. Spend goes up, installs don't move enough, and suddenly the acquisition plan feels grim.
A weak listing wastes both organic traffic and paid traffic. The channel changes. The problem doesn't.
There's another local wrinkle. NZ and AU users often respond better to listings that feel native to the market. Not overdone. Not forced. Just familiar. Currency, spelling, examples, category language, even the tone of the screenshot copy can make the difference between “this looks built for me” and “this looks imported”.
ASO becomes more important once competition tightens, and that's exactly the environment we're in. The broader digital market is mature enough that attention is expensive, and app publishers are competing inside that pressure. If you leave your listing generic, larger players usually beat you on brand recognition alone.
For local founders, that means one thing. You don't win by being louder. You win by being clearer, more relevant, and easier to trust at the exact moment someone searches.
ASO has two jobs. First, it helps people find your app. Second, it helps them decide to install it. Founders often focus on one and neglect the other.
That's a mistake because visibility without conversion is just expensive disappointment. Conversion without visibility is a beautiful shop on a side street nobody walks down.
According to OneSignal's explanation of how app store optimization works, the New Zealand digital advertising market reached about NZ$2.08 billion in 2024. The same source also points to a 3.6% average conversion figure from a 2020 US AppTweak dataset for all categories in the US App Store, while a strong store page can convert at 33.7%. That gap is why good ASO punches above its weight. It can grow installs without buying more traffic.
This is the side typically considered first. Keywords, title structure, category choice, localisation, and metadata all sit here.
If a founder asks me where to start, I usually say this: learn the language your users already use. Not your internal product jargon. Not the phrase your board likes. The words customers type when they want the outcome.
Here are the main discoverability levers:
If you need a local starting point for that work, this guide to keyword research in New Zealand is useful because it forces you to think about search language through a regional lens.
At this stage, many listings underperform. They rank for some terms, traffic comes through, but installs stay soft.
The usual causes are easy to spot once you know the pattern. The icon looks generic. The screenshots show features instead of outcomes. The opening copy is vague. The page doesn't answer the user's first question, which is almost always some version of “Why this app, and why now?”
Your first screenshot should sell the promise. The second should prove it. The third should reduce doubt.
A practical way to think about it is like a shop window:
| Element | What it does |
|---|---|
| App title | Signals relevance quickly |
| Icon | Builds instant recognition and trust |
| Screenshots | Show the problem solved and the experience |
| Description | Adds clarity and reassurance |
| Ratings and reviews | Reduce risk for hesitant users |
This part sits between discoverability and conversion. Reviews influence trust, and they also tell you what users value or hate. Update notes can reinforce momentum. Performance problems can drag down the page experience even if the listing itself is tidy.
Good ASO isn't one metadata pass and done. It's ongoing product marketing with feedback loops. The teams that treat it that way usually get sharper over time. The teams that upload a listing once and forget it tend to wonder why organic growth feels patchy.
Theory is fine. The practical question is what to change on Monday morning.
The first practical move is to stop treating Apple and Google as if they reward the same setup. They don't. Similar audience, different indexing logic.
According to AppTweak's guide to why ASO is important, Apple prioritises the title, subtitle, and a hidden keyword field, while Google Play scans the title, short description, and long description. So no, you can't copy and paste one keyword plan into both stores and expect a clean result.
Imagine it as packing for two trips with one suitcase. Same traveller, different weather.
On Apple, you need to be economical. Priority keywords belong in the title and subtitle, then the hidden field supports coverage. On Google Play, the description fields matter more because Google reads more of the text.
A simple working approach looks like this:
Founders love feature dumps. Users don't.
If the screenshots say “dashboard”, “analytics”, “notifications”, “profile”, you're describing furniture in the room. You're not explaining why the room matters. Better screenshot copy leads with outcomes and friction removed.
For example, instead of naming the feature, show the payoff. Save time. Book faster. Track spending clearly. Manage staff on the go. Learn with short daily lessons. You get the idea.
A few rules I use often:
Descriptions tend to be either overstuffed or strangely empty. Neither works.
Your description should make the app easy to understand, reduce hesitation, and support the keywords that belong there for the relevant store. For Google Play especially, structured copy helps. Use short paragraphs, crisp phrasing, and plain language.
For NZ and AU founders, localisation often shows up in small choices:
| Listing element | NZ and AU advice |
|---|---|
| Spelling | Use local English where it fits your market |
| Currency references | Match NZD or AUD when relevant |
| Examples | Use familiar local contexts, not imported ones |
| Tone | Clear and grounded beats hype-heavy copy |
Indeed, some of the most impactful ASO wins come from unglamorous cleanup. Wrong category. Unclear subtitle. Old screenshots after a redesign. Reviews left unanswered. Messaging that still reflects version one of the product.
That stuff doesn't feel exciting, but it shapes how both the store and the user interpret your app. Boring work often wins.
Founders usually ask the wrong question here. They ask, “Did installs go up?” Useful, yes. Sufficient, not really.
You need to separate a traffic problem from a conversion problem. If the app page isn't getting enough qualified visitors, metadata and keyword targeting may be the issue. If traffic is steady but installs lag, the listing itself is the likely culprit.
According to AppsFlyer's ASO measurement guidance, you should wait until your app page has at least 400 visitors before calling an ASO experiment meaningful. That helps you avoid reacting to noise and makes it easier to tell whether the problem is discoverability or conversion.
Change one major variable at a time. Otherwise you'll get movement, but no insight.
That sounds obvious, yet teams break this rule constantly. They change the icon, screenshots, subtitle, and description together, then try to infer what caused the lift or drop. You can't learn much from that.
The most useful ASO readout usually comes from a mix of indicators, not one magic metric:
For teams that already think in analytics terms, this guide on how to measure website performance is a decent mental model for the broader discipline. Different channel, same principle. Don't guess when you can instrument.
AppTweak, App Store Connect, Google Play Console, AppsFlyer, and Firebase can all help. They make the work less foggy. Still, tools won't save weak thinking.
A strong ASO process looks simple from the outside. Research user language. Map it to the store correctly. Improve the creative. Measure patiently. Repeat. Not glamorous, but that's the job.
If you want the short working version, keep this nearby before launch and after every meaningful update.
Good ASO feels deceptively simple. That's because the principles are easy to explain. The hard part is discipline. Relevance, clarity, iteration, patience. Again and again.
If you're building or scaling an app in this region, NZ Apps is worth keeping on your radar. It covers the NZ and AU app market with founder-focused guides, company roundups, and practical resources that help local teams get clearer on positioning, growth, and who's who in the ecosystem.
Add your NZ or Australian app or tech company to the NZ Apps directory and get discovered by founders and operators across the region.
Get ListedReach tech decision-makers across New Zealand and Australia. Sponsored and dofollow editorial links, permanent featured listings, and sponsored articles on a DA30+ .co.nz domain.
See Options