Your app is great. So why can't anyone find it?
You've done the hard yards. Late nights, too much coffee, a slightly feral launch week, and a team that's poured real care into building something useful. You hit publish in the App Store or Google Play and then... not much happens. A few installs, maybe a couple of kind reviews from mates, but no real momentum. That sting is familiar to plenty of founders across New Zealand and Australia.
The annoying truth is simple. A good app doesn't sell itself. Not in crowded categories, and definitely not when you're up against global brands with bigger budgets, louder brands, and entire teams focused on growth. Building the product is only half the job. Getting discovered is the other half, and it's a different craft.
That's where app store optimization tips matter. Not fluffy growth-hack nonsense. Real store-page work that helps the right users find you, trust you, and install. Think of ASO as supermarket shelf space, shop signage, packaging, and the first ten seconds of a sales pitch rolled into one.
For Kiwi and Aussie founders, there's also an edge here. We don't need to look generic and global from day one. In many cases, leaning into local relevance, local wording, local trust signals, and local use cases is exactly how you beat bigger players.
Let's get into it.
Most founders start with the words they use internally. That's usually the wrong place to start.
Users don't search for your roadmap language. They search for the problem in front of them. A Kiwi fintech founder might love “accounts receivable automation”, but a small business owner may type “invoice software NZ”. That gap matters more than people think.
Tools like Sensor Tower, Mobile Action, and your own store analytics are useful because they show how the market talks. If you're building for ANZ, I'd also look for regional modifiers and spelling variations. “Organise” and “organize” can both matter. So can “NZ”, “New Zealand”, “AU”, and “Australia”, depending on who you're targeting.
On Google Play, the first 80 characters of your long description appear as the short description, so your main keyword needs to sit inside that exact window if you want it visible in search results. Semrush's app store optimization guide calls out that mechanic, and it's one of those small details that changes real outcomes.
That doesn't mean stuffing awkward phrases everywhere. It means being deliberate. Put the most important phrase in the title or subtitle if it fits naturally, then support it with adjacent terms in the rest of the listing. If your app helps tradies invoice faster, say that plainly.
Practical rule: If a phrase sounds clunky when you read it aloud, it's probably clunky on the store page too.
A few grounded moves help here:
If you want a local lens on phrasing and search behaviour, this NZ keyword research guide for app and software teams is a handy reference, and so are these App Store metadata insights for mobile teams.
Titles do two jobs at once. They help you rank, and they help a human decide whether to tap.
That tension is where a lot of listings go sideways. Founders either write a pure brand title that means nothing to a new visitor, or they cram so many keywords into the name that it reads like spam. Neither is great. If you're Xero or Canva, sure, your brand can carry weight. If you're an earlier-stage app, clarity usually beats cleverness.
For ANZ founders, a title can also signal local fit. “Invoicer Pro NZ” won't win design awards, but if your buyer is a New Zealand accountant scanning search results fast, that local cue can do useful work.
Mobile screens cut titles off quickly. So front-load the useful bit. Lead with the core use case or the strongest keyword, then bring in the brand if the name still reads naturally. The subtitle on Apple gives you extra room to add context, not extra room to repeat yourself.
If the app helps clinics handle bookings, say that. If it's built for Aussie allied health providers, say that too, provided it doesn't turn into word soup. “Health bookings for AU clinics” is better than a vague slogan nobody can parse.
There's another small formatting win that people miss. Using digits instead of spelling out numbers saves space and matches how people search, because Adjust notes that 90% of consumers type digits for numbers in queries. That's useful if your app competes around phrases like “top 5 AI tools NZ” or “3 step budgeting”.
The test is boring but effective. Read the title and subtitle aloud. If it sounds like something a normal person would say, you're on safer ground. If it sounds like metadata stitched together by committee, trim it back.
Your icon has to work ridiculously hard for such a tiny square.
It shows up in search results, browse pages, featured slots, and later on the user's home screen. If it's muddy, generic, or over-designed, people skip past it. If it's clear and distinct, it buys you a second look. That second matters.
Here's the visual reminder. Small size changes everything.
Notion and Slack are a useful contrast. Notion gets away with restraint because the brand is already widely recognised. Slack leans on a bolder, more instantly recognisable shape and colour system. Both work. They just solve different problems.
At thumbnail size, fine detail disappears. Thin lines vanish. Tiny text turns into fuzz. Gradients can collapse into a blob. So keep the shape simple, the contrast clean, and the meaning obvious enough that someone can spot it while half-distracted on a train or in a queue for flat whites.
If you're a local app, a subtle ANZ cue can help if it doesn't clutter the mark. A regional palette, a distinctive motif, or a familiar visual personality can make you more memorable than another generic SaaS blue square. Pushpay is a good reminder that a strong colour identity can carry a lot of brand recognition.
A few practical checks help:
Good icon work usually sits beside good product design. If the listing looks polished but the app feels rough, users notice fast. If you're tightening both, this NZ UI and UX design consultant resource is worth a look.
Screenshots aren't decoration. They're sales material.
A lot of teams still treat them like a gallery of features. That's backwards. Users don't care that you have filters, folders, dashboards, and sync. They care what changes for them after they install. Better screenshots make that outcome obvious.
Local relevance becomes particularly interesting for Kiwi and Aussie apps. Even though we all speak English, store visuals still feel “foreign” when they show the wrong context, wrong spelling, or weirdly American workflows. If your screenshots show GST handling, local currency, or a familiar business setting, trust goes up.
Lead with the strongest payoff in the first screenshot. Not the menu. Not the settings page. The payoff.
Notion is good at showing workflows instead of feature laundry lists. Headspace does something similar emotionally. It sells the calmer version of you, not merely the interface. For product, finance, or SaaS apps, the same logic applies. Show the task getting easier, faster, clearer.
Video can help too, but only if it works without sound. Branch notes that 80% of users watch preview videos with sound off, which is exactly why text overlays matter so much. If the story only works with narration, you've probably lost the room already.
Most preview videos fail for a very ordinary reason. They assume the viewer is paying full attention. They're not.
Keep the motion honest. Real app interactions beat glossy hype reels most of the time. Add short text overlays, make the sequence easy to follow, and design the first seconds to land fast. If the value takes too long to appear, users move on.
Descriptions still matter, just not in the way many teams think.
Users often won't read every line. They scan. They stop early. They look for reassurance. So the opening lines need to carry the pitch, not the housekeeping. If your first paragraph starts with corporate waffle, you're leaking installs.
This is especially true on Google Play, where users often make a snap call from that visible snippet. So don't waste those opening lines on “Welcome to” or “our mission is”. Lead with the problem you solve and who you solve it for.
Xero is a useful model in spirit because it tends to be direct about who it serves and what the product helps with. Calm does something similar from a different angle, leading with the emotional result before unpacking features. Different category, same principle.
If you're selling into NZ or Australia, this is also the place to mention local trust cues. Things like local payment support, compliance detail, or regional fit belong near the top if they matter to the buyer. That sort of specificity calms people down. And calm converts.
One detail people often miss on the product side also matters here. Some of the strongest conversion gains don't come from metadata at all. A top ASO practitioner said that for apps taking two weeks to build, one week is often spent refining onboarding and the paywall because those moments shape conversion more than title tweaks. That idea came up in this ASO discussion on YouTube, and it rings true. If your listing promises one thing but the onboarding fumbles it, the store page won't save you.
For the writing itself, keep it tidy:
If your team is trying to speed up description drafting while keeping the message coherent, this piece on streamlining product description workflows with AI is a useful prompt.
A founder in Auckland spends weeks tightening the title, screenshots, and copy. Then a prospect opens the listing, sees a 3.7 rating with a few unanswered complaints about GST bugs, and drops off. That happens more often than teams like to admit.
Ratings shape trust fast. Reviews also tell the stores whether real users are having a good experience after install, which is why I treat review management as part of growth ops, not admin.
For NZ and AU apps, the comments often reveal your advantage against larger overseas competitors. Users mention local tax rules, bank connections, spelling, support hours, or whether the app fits how teams work here. If someone writes, “Finally, a roster app that handles public holidays properly in Australia,” that review does selling for you. Protect it. Surface more of it.
A flat corporate reply does not help. A useful reply names the issue, gives a next step, and shows you understood the local context.
If a reviewer flags payday filing problems in New Zealand, say that directly. If an Australian customer hit a superannuation or BAS-related issue, answer with that detail. Future buyers read those responses. They are checking whether your team is present, competent, and close enough to the market to fix the right things.
Speed matters too. A stale one-star review with no reply suggests the product team is asleep. A calm response within a day or two suggests the opposite.
One caution: Ask for reviews after a clear success moment.
Good timing beats aggressive prompting. Request a rating after a user completes a job, sends an invoice, books a shift, or reaches a milestone they care about. Do not interrupt during onboarding friction, failed payments, or login issues. That just creates negative reviews you could have avoided.
I also recommend tagging review themes every week. Keep it simple. Billing, bugs, feature gaps, onboarding confusion, and local compliance are usually enough. Patterns show up quickly. If ANZ users keep mentioning the same issue, fix the product first, then reply to the old reviews once the fix is live. That closes the loop and often wins back trust.
The practical goal is straightforward:
Teams that do this well usually see better conversion from the same traffic. They also get sharper market feedback, which matters when you are competing with bigger US apps that still feel a bit off in our part of the world.
The temptation with ASO is to redesign everything at once. Resist it.
When you change the icon, screenshots, title, and description together, you create a nice internal launch moment and terrible learning conditions. You might get a lift, or a drop, and still have no idea why. Founders hate hearing this because it's slower. It is slower. It's also how you learn what works.
Google Play experiments and Apple's product page testing tools are useful because they let you test one variable at a time. Start with high-impact elements. Usually that means icon, first screenshot, or title message. Description changes matter too, but they often sit lower down the priority list than teams expect.
One of the more useful tests for ANZ apps is regional language. “Organise” versus “organize”. “Built for Australian businesses” versus “made for growing teams”. Sometimes the local phrase wins because it feels more credible. Sometimes it loses because the broader phrase is clearer. You won't know until you test.
I also like testing different value framings. A founder may love the feature-led version. The market may prefer the benefit-led one. “Team scheduling” might underperform “Fill shifts faster”. That's a messaging lesson, not just an ASO lesson.
Keep your process tight:
Seasonality can play a role as well. EOFY messaging, back-to-school use cases, or summer travel angles can all change how a listing lands in Australia and New Zealand. Not every category needs seasonal creative, but when it fits, it fits.
A founder in Auckland can ship the same app listing as a competitor in San Francisco and still lose the install. The product may be solid. The listing just feels imported.
That is the opening ANZ teams should use.
Localization for New Zealand and Australia often has nothing to do with translating into another language. It means making the app page feel built for the people reading it. Spelling matters. Currency matters. Local compliance cues matter. So do the examples, screenshots, and tone of voice. Australian buyers usually respond well to clear, plain claims. Kiwi buyers often prefer the same clarity with less chest-beating.
Global apps often iron all of that out into generic international English. You can use your regional identity as an advantage instead of hiding it.
If the app supports New Zealand payroll, say New Zealand payroll. If it handles Australian BAS, GST, or local payment rails, put that in the listing where buyers can see it fast. Founders sometimes worry this will make the product feel smaller. In practice, it often makes the product feel more credible.
That trade-off matters in ANZ. A broad message can attract more impressions. A local message usually gets better-fit installs if the product is a strong fit for this market.
Preview video is part of this too. If the video only makes sense with voice-over, plenty of users will miss the point. Localised preview videos with clear text overlays usually perform better for sound-off viewing because the value proposition is obvious straight away. For ANZ apps, that means showing local use cases, local terminology, and interface moments that look familiar to users here.
A few practical ways to handle it:
Local relevance is trust, and trust lifts conversion. In a market like ours, where buyers are used to overseas products that almost fit, "built for here" can be the difference between a glance and an install.
Some apps are easy to categorise. Plenty aren't.
A project tool might fit in Productivity, Business, or even a niche subcategory depending on the platform. A health app might be Health and Fitness, Medical, or Lifestyle. Category choice matters because it shapes your competitive set. Pick badly, and you're standing in the wrong aisle of the supermarket.
Founders often choose the category that sounds most flattering internally. That's not the job. The job is to help the right users find you, and to place you against rivals you can realistically compete with.
Notion can live in Productivity because it has broad recognition and category-spanning use. A smaller workflow app may struggle there and do better in Business if that puts it in front of more qualified users. Same product, different shop window.
For ANZ teams, there's a trade-off. The big mainstream category may have more overall traffic, but the adjacent category may offer more visibility and a more relevant audience. If you're a local fintech, Finance can be the obvious fit, but Business may sometimes be a stronger strategic choice if the buyers are really operators and owners rather than consumers.
Choose the category your customer would expect, not the category your team prefers in a strategy deck.
Check the top competitors. Check the browse results. Check whether the category story matches your screenshots and title. If there's a mismatch, users feel it fast. And if you sit in the wrong category long enough, your whole listing starts working against itself.
A founder spends weeks polishing screenshots, rewrites the subtitle three times, finally gets more installs, then watches retention fall through the floor. I've seen that pattern a lot with ANZ apps. The listing got the click. The product did not earn the second session.
Store algorithms pay attention to what happens after install. If people open the app, get confused, abandon onboarding, or churn before they hit value, your ranking tailwind fades fast. That's why ASO and product work sit closer together than many teams want to admit, especially in smaller NZ and Australian markets where a rough first experience gets reflected in reviews and word of mouth quickly.
For local founders, this is one of the few areas where you can beat bigger offshore competitors. A global app may have a prettier listing and a bigger budget. You can still win if your product feels more relevant on day one. Use local date formats, local billing cues, AU and NZ terminology, and examples that match how people here work. A tradie app should help someone send the first invoice fast. A booking app should get a salon or clinic to its first confirmed appointment without extra setup. That kind of early success improves retention, ratings, and search momentum at the same time.
The strongest engagement signals usually come from a few plain things done well:
One trap I see in the NZ/AU SaaS scene is over-explaining during onboarding. Founders want users to understand every feature before they do anything. That usually hurts activation. Show the first result, then teach. If your listing promises speed, the app needs to feel fast within the first minute.
Reviews fit into this too, but the point is not chasing stars for the sake of it. Good review management works best when the product already creates a clear success moment. Prompt too early and unhappy users will tell you exactly what's broken. Respond well and fix the issue, and you often recover both the customer and the rating.
If your team is revisiting the product layer behind the listing, these mobile app development fundamentals for NZ teams are worth revisiting too.
| Item | Implementation Complexity 🔄 | Resource Requirements ⚡ | Expected Outcomes ⭐ / 📊 | Ideal Use Cases 💡 | Key Advantages ⭐ |
|---|---|---|---|---|---|
| Keyword Research and Strategic Placement | 🔄 Medium, ongoing analysis & updates | ⚡ Low–Medium, keyword tools + analyst time | ⭐ Improved organic discoverability; ranking changes in ~3–6 weeks | 💡 Regional SaaS, niche apps targeting NZ/AU search intent | ⭐ Targets intent with low CAC; regional keyword edge |
| Compelling App Title and Subtitle Strategy | 🔄 Low, copy iteration within limits | ⚡ Low, copywriting + quick tests | ⭐ Higher CTR from search & browse; immediate measurable lift | 💡 Apps needing clear value proposition in SERPs | ⭐ Boosts click-through and reduces mismatched installs |
| Eye-Catching App Icon and Visual Design | 🔄 Low–Medium, design + scalability tests | ⚡ Medium, designer time, A/B testing | ⭐ Increased tap-through (often 20–30%) and brand recall | 💡 Consumer, productivity, and visual-competitive categories | ⭐ Visual differentiation; fast-to-test branding wins |
| High-Impact App Preview Screenshots and Video | 🔄 Medium, storytelling + production | ⚡ Medium–High, design, copy, video production | ⭐ Strong conversion impact (screenshots 30–50%; video up to +80%) | 💡 Feature-rich apps, workflow demos, regional localization | ⭐ Shows value fast; major conversion lever |
| Persuasive App Description That Converts | 🔄 Low, structured copywriting & maintenance | ⚡ Low, writer + periodic updates | ⭐ Converts engaged viewers; supports store SEO/indexing | 💡 Enterprise/SaaS or apps with nuanced value propositions | ⭐ Addresses objections; adds secondary keyword reach |
| User Reviews and Ratings Management | 🔄 Medium, continuous monitoring & responses | ⚡ Medium, support team + monitoring tools | ⭐ Higher conversions and product feedback; affects ranking | 💡 Apps with active user support needs; AU/NZ regional markets | ⭐ Social proof; drives product improvements and trust |
| A/B Testing Elements for Continuous Improvement | 🔄 High, experiment design & statistical analysis | ⚡ Medium, multiple assets + analytics tooling | ⭐ Incremental, compounding uplifts; data-driven wins | 💡 Apps with sufficient traffic optimizing icons/titles/screens | ⭐ Removes guesswork; reveals regional messaging winners |
| Localization and Regional Relevance | 🔄 Medium–High, translation + cultural adaptation | ⚡ Medium–High, native reviewers, localized assets | ⭐ ~15–25% higher conversions in target regions | 💡 AU/NZ-focused apps or those entering regional markets | ⭐ Builds trust; less competitive regional keyword rankings |
| App Store Category and Subcategory Positioning | 🔄 Low, strategic selection with some risk | ⚡ Low, competitor research only | ⭐ Better browse placement and more qualified traffic | 💡 Apps straddling categories seeking lower competition | ⭐ Free strategic lever to reduce competitive pressure |
| Engagement Metrics and In-App Signals to Search Algorithms | 🔄 High, product, analytics, and retention work | ⚡ High, development, analytics, onboarding investments | ⭐ Strong long-term ranking and sustainable organic growth | 💡 Apps prioritizing retention and lifetime value | ⭐ Compounding organic visibility via retention signals |
Feeling slightly overloaded? Fair enough. There are a lot of moving parts here, and ASO has a sneaky way of looking simple from a distance and fiddly up close. One field affects another. One screenshot changes the meaning of the title. One poor onboarding moment can undo a polished listing. That's normal. It's also why steady operators tend to beat frantic ones.
The good news is you don't need a perfect store page by Friday.
You need momentum.
Start with the bottleneck that's most obvious. If your title is vague, rewrite it. If your icon looks like it was approved at 1.00 am during launch week, fix it. If your screenshots show features but not outcomes, rebuild the first three. If your rating is slipping, sort out review responses and in-app prompts before anything else. The work compounds, even when it doesn't feel dramatic in the moment.
And keep the ANZ angle in view. This matters. A lot of founders assume they need to look more global, more neutral, more generic to compete. Often the opposite is true. Local relevance is not a small flourish. It's a strategic edge. New Zealand and Australian users notice when an app feels built for them. The wording lands better. The trust signals feel stronger. The use cases make sense. You're not trying to trick anyone into thinking you're bigger than you are. You're proving you understand the market better than the giant players do.
That's a powerful place to stand.
I'd also keep one healthy contradiction in mind. ASO is partly about visibility, yes. But the listings that perform best usually come from teams that treat ASO as product communication, not keyword decoration. The title should reflect the actual value. The screenshots should preview the actual payoff. The onboarding should cash the cheque the store page writes. When those things line up, growth gets less brittle.
So pick one change this week. Not ten. One.
Maybe it's tightening the first 80 characters on Google Play. Maybe it's rewriting the subtitle so a stranger understands what the app does. Maybe it's creating a silent-friendly preview video with text overlays for local users. Maybe it's cleaning up review response workflows so people stop feeling ignored.
Small improvements, repeated often, beat one heroic metadata sprint every time.
You've already built something worth shipping. Now help the right people find it, trust it, and stick around long enough to see why it matters.
If you're building or scaling an app in New Zealand or Australia, NZ Apps is a smart place to get regional visibility, local credibility, and a stronger foothold in the market. The site covers the app and tech ecosystem across NZ and AU, which makes it useful not just for founders, but for operators, investors, and marketing teams looking for quality local exposure and relevant industry context.
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