Choosing and Setting Your App's Package Name

Your package name is a small field in the app creation form, but it carries more weight than any other setting. It is the permanent, unchangeable identity of your app on Google Play. Getting it wrong (or changing it later) requires creating an entirely new Play Store listing from scratch, losing all your installs, ratings, and reviews. This guide explains what it is, the rules it must follow, and how to choose wisely.

What Is a Package Name?

Every Android app needs a globally unique string that identifies it. This is the package name (sometimes called the application ID). It is used by:

• The Android operating system: to install, update, and distinguish your app from every other app on a device
• Google Play: the permanent URL of your store listing (play.google.com/store/apps/details?id=your.package.name)
• Firebase, AdMob, and other integrations: to tie SDK configurations to the correct app

Because it serves as the permanent unique key for your app, it can never be changed after you publish your first release to Google Play. If you change it, Google Play treats it as a brand-new app with no history.

The Required Format

Android package names follow reverse domain notation. The structure is:

tld.domain.appname

For example, if your website is mybakery.com, your package name might be:

com.mybakery.app

Or more specifically:

com.mybakery.orderapp

Rules Your Package Name Must Follow

• Lowercase letters (a–z), digits (0–9), and underscores (_) are allowed
• Each segment (part between dots) must start with a letter, not a digit or underscore
• At least two segments separated by a dot are required: mybakery alone is not valid; com.mybakery is
• No hyphens (-), spaces, or special characters
• No uppercase letters (Android allows them, but they are strongly discouraged and inconsistently handled)

WebToAppConvert will validate your package name in real time and flag any violations before you proceed.

How WebToAppConvert Suggests a Package Name

When you enter your website URL, the app automatically generates a suggested package name based on your domain. For example:

• URL: https://mybakery.com → suggestion: com.mybakery.app
• URL: https://shop.acmecorp.com → suggestion: com.acmecorp.shop
• URL: https://my-blog.wordpress.com → suggestion: com.myblog.app (hyphens stripped)

The suggestion is a safe starting point. You can accept it or customise it, just ensure it meets the format rules above and reflects your actual brand.

Choosing the Right Package Name

Use Your Own Domain

The most reliable approach is to base the package name on a domain you own. If you own acmecorp.com, use com.acmecorp.yourappname. This way:

• The name is inherently unique (you own the domain)
• It signals professional ownership to Google Play reviewers
• It links the app identity to your actual brand

Include a Meaningful App Suffix

The third segment should describe what the app does or is, not just be .app for every app. Examples:

• com.mybakery.orders: for an ordering app
• com.mybakery.loyalty: for a loyalty card app
• com.mybakery.app: acceptable as a generic identifier if you only have one app

This matters most if you plan to publish multiple apps. com.acmecorp.app and com.acmecorp.vendor are immediately distinguishable; two apps both trying to use com.acmecorp.app would conflict.

What to Avoid

• Generic names like com.android.myapp: The com.android namespace is reserved by Google and will be rejected
• Brand names you don't own: Using com.google.mybakery or com.facebook.shop violates Play Store policies
• Temporary or test names: Names like com.test.app or com.example.test read as unprofessional and the word "example" is associated with tutorial placeholders
• Overly long names: Keep it readable. com.mybakery.freshartisanbreadorderingsystem is technically valid but unwieldy

What Happens If You Use a Package Name Already on Google Play?

Package names are globally unique on Google Play. If another app (by any developer) already uses your package name, your upload will be rejected with an error. WebToAppConvert cannot check Play Store availability for you before you build, but you can search manually at play.google.com/store/apps/details?id=your.package.name. If the page 404s, the name is available.

Can You Change the Package Name Later?

You can change the package name in WebToAppConvert at any time before publishing to Google Play. After submitting your first release:

• Changing the package name in WebToAppConvert and rebuilding produces a different app as far as Android and Google Play are concerned
• Existing users will not receive an update: their installed app will stay at the old version indefinitely
• You will need to create a new Google Play listing from scratch
• All installs, reviews, and ratings on the old listing are permanently lost

This is why choosing correctly before the first release matters. For debug builds (testing only, never published to Play), you can use any package name freely: those builds are not on the Play Store, so changing the name has no permanent consequences.

Practical Checklist

1. Based on a domain you own
2. All lowercase, no hyphens, no spaces
3. At least two segments (e.g., com.yourdomain.app)
4. Does not start with com.android, com.google, or any namespace you don't own
5. Describes the actual app, not just "app" if you have or plan multiple apps
6. Checked on Google Play for conflicts if you are unsure

Once confirmed, copy it exactly. The package name is case-sensitive and must be identical in every build you publish as an update to the same Play Store listing.