App Name Availability: How to Check Before You Launch

To check app name availability, search the exact name and close variants in Apple’s App Store and Google Play, review the publishers and product categories, then check domains and the social platforms you will actually use. Confirm the proposed listing in the relevant developer console and conduct separate company and trade-mark checks before committing. A search with no results is a useful observation—not a reservation, a promise of approval or permission to use a name.

This guide is for a founder who already has a few possibilities and wants to choose one before paying for a domain, artwork or launch campaign. You do not need another hundred suggestions. You need to understand which of your finalists can work across the places customers will find you.

What does an app name availability check actually prove?

There is no single register that clears a name everywhere. A domain result, an app listing, a username and a trade mark answer different questions. Keep these results separate so that one encouraging green indicator does not hide an unresolved problem.

1. Search Apple’s App Store and Google Play separately

Start with the exact spelling, then try the spaced version, a likely misspelling and the name as someone might write it after hearing it. Repeat the search in each launch market. Open the result pages rather than deciding from the first search snippet. Record the publisher, what the app does, its website and why the result might confuse your intended customer.

On Apple, a public search is not a substitute for checking the app record. Apple’s App Store Connect guidance explains what happens when an app name is unavailable and how names are used per localization. Do not assume that an empty public result means the developer console will accept your chosen name.

On Android, distinguish the visible app title from the package name. Google’s setup guidance says package names are unique and permanent; the app name is a separate listing field with a 30-character limit. Creating an app record is not a global claim over the words in its title. Follow the console’s validation and policies as well as researching existing products.

2. Separate identity conflicts from discoverability problems

Two different problems can appear in the same search. A similarly named app serving the same audience may create an identity conflict. A name buried among unrelated dictionary-word results may instead be hard to find. Both matter, but they call for different decisions. The first needs closer conflict review; the second may need a clearer name or more descriptive listing.

For each finalist, ask a person unfamiliar with your project to find it from the spoken name and a one-sentence description. Note spelling mistakes and which existing results they choose. This is a small usability exercise, not representative market research. It can still expose practical friction before you build your whole identity around a name.

A distinctive name does not need to contain every keyword. Apple describes App Store discovery as involving text relevance and customer behaviour, including downloads and ratings. A name alone cannot guarantee visibility. Use accurate descriptive metadata, and test whether the listing explains the product. Google also warns against repetitive or irrelevant keyword use in its listing guidance.

3. Check the domain and the social accounts that matter

Choose two or three customer-facing channels before checking everything. For a developer tool that might be GitHub and X; for a visual consumer app it could be Instagram and TikTok. An exact handle on a platform you will never use is less valuable than a clear identity on the channel where customers already look for you.

A missing profile page does not prove that you can register its username. Treat platform search as evidence, then confirm claimability through the platform’s own process. If the exact handle is unavailable, consider a consistent, honest modifier such as “get” or “app”, but do not use a modifier to disguise a confusingly similar competitor name.

Compare the purchase and renewal costs of your domain options before buying. A different extension can be workable, but it does not resolve a conflict with an established business using the same name. For that specific decision, see our .com versus .ai guide. Recheck with the registrar immediately before purchase.

4. Keep a decision sheet—not just a score

Use one row per finalist. Record the launch market, date, exact search, source link, result and next action. This prevents a vague memory of “we checked it” from replacing evidence. The example below is hypothetical; it is not a live availability claim about any real name.

A high naming score does not overrule an unresolved conflict. Equally, an unrelated app result should not automatically decide the outcome without context. Write down why the chosen name fits your product, what compromises you accept and which checks remain open. If the record does not support the choice, keep evaluating rather than manufacturing certainty.

5. Use NamoLux to bring the checks together

If you have names already, Bulk Check accepts up to 50 candidates and checks .com, .io, .co, .ai, .app and .dev. 3 Bulk Check runs per UTC calendar month plus 1 Name Sprint per UTC day. Names and domain evidence are free. Founder Signal, app/social checks, guided register checks and Brand Kits require paid access. Starter costs £19 once, with no subscription. 25 Bulk Check batches, 100 individual Founder Signal assessments, 25 Name Sprints, 2 Brand Kits and one saved project. These are total purchased credits, not monthly allowances.

If you need a starting point, Name Sprint turns a brief into a focused shortlist with domain evidence. Starter unlocks the optional app-store and social checks from your name cards. Founder Signal remains a separate decision-support assessment, not an app-store ranking prediction. Scoring each candidate uses one assessment credit; scoring all 50 names in a Bulk Check uses 50 credits.

The app checks support UK and US market selection. Results can include matching apps and publishers, or an unresolved status with a manual route when verification cannot complete. Social checks include an automated exact GitHub-handle lookup and manual verification links for other supported platforms. These optional checks do not change the Founder Signal score or automatically reject a candidate.

Buy Starter when the comparison and launch tools will help you make a decision. See the pack and its fixed allowances before purchasing. Credits do not reset monthly, and there is no automatic renewal. Once you have made your decision and completed the outstanding checks, Brand Launch Kit helps turn the chosen name into a visual identity and launch materials. Domain registration is a separate purchase.

Before you commit: the final checklist

• Search exact and similar names in both app stores for your intended markets.
• Review publishers, categories and websites behind potentially confusing matches.
• Check the app name in the developer console; do not rely on public search alone.
• Confirm domain availability and renewal costs directly with the registrar.
• Verify the social handles you plan to use through the platforms themselves.
• Complete separate company and trade-mark searches and record unresolved questions.
• Save the evidence date and your reason for choosing the name before commissioning launch assets.

For the UK, the IPO search service lets you investigate similar trade marks. Check the relevant official registers in every market you intend to serve and seek qualified advice for a potential conflict. The broader business-name checking guide explains how those checks differ. This article and NamoLux’s preliminary screening are not legal clearance.