Back to Guides & Tutorials

How to Choose an Android Package Name for Your Website App

CW
ConvertWebsites Engineering Team
Mobile SDK Architects & Core Contributors
Published: 2024-07-01 4 min read ✓ Verified Guide

Everything you need to know about Android package names. Learn what they are, why they matter, and how to choose the right one for your app.

When you generate an Android app from your website, the online converter will often ask you for an Android Package Name (sometimes called an Application ID).

To a beginner, this looks like a random string of text written backwards (e.g., com.mywebsite.shop).

This string of text is actually one of the most important technical elements of your app. Once you set it and publish your app, you can never change it.

In this guide, we will explain what a package name is, why it matters, and how to choose the perfect one for your website app.

What is an Android Package Name?

An Android Package Name is a unique identifier for your application on the Android operating system and the Google Play Store.

Think of it like a Social Security Number or a passport number for your app. No two apps in the world can have the same package name. When Google Play processes your app, it uses this exact string to identify it.

If your app is published on the Play Store, the package name will actually appear in the URL of your app's store page. For example, the package name for the official Facebook app is com.facebook.katana, which makes its Play Store URL: https://play.google.com/store/apps/details?id=com.facebook.katana

The Format of a Package Name

Package names are historically written in "reverse domain name notation." This convention was created to guarantee global uniqueness, assuming that domain names are already unique to their owners.

The format typically looks like this: [top-level domain].[your company name].[your app name]

For example:

  • com.nike.store
  • net.example.blog
  • co.uk.mybusiness.app

Rules for Creating a Package Name

While you can technically make your package name almost anything, you must follow these strict Android rules:

  1. At least two segments: It must have at least one dot (e.g., com.myapp). You cannot just use a single word like myapp.
  2. Allowed characters: You can only use lowercase and uppercase letters (a-z, A-Z), numbers (0-9), and underscores (_).
  3. No starting numbers: A segment cannot start with a number. (e.g., com.123store is invalid, but com.store123 is fine).
  4. No dashes or spaces: You cannot use hyphens or spaces. If your domain is my-store.com, your package name should remove the dash: com.mystore.app.

How to Choose Yours

The easiest and most professional way to choose your package name is to simply reverse your website's URL.

Scenario A (A Standard Domain):

  • Your website: yourshop.com
  • Your package name: com.yourshop.app

Scenario B (A Country Code Domain):

  • Your website: yourblog.co.uk
  • Your package name: uk.co.yourblog.app

Scenario C (Multiple Apps): If you plan to release multiple apps under the same brand (e.g., a customer app and a delivery driver app), you should distinguish them at the end:

  • Customer App: com.yourbrand.customer
  • Driver App: com.yourbrand.driver

A Warning: You Cannot Change It Later

We cannot stress this enough: Once you upload an app to the Google Play Store with a specific package name, it is permanently locked.

If you realize a year later that you misspelled your package name, or you rebrand your company and want a new package name, you cannot simply update your existing app. You would have to generate a brand new app, create a brand new listing on the Play Store, and try to convince all your existing users to download the new app.

Choose your package name carefully, double-check your spelling, and keep it forever.

Conclusion

Choosing an Android package name is a simple but permanent decision. By following the standard reverse-domain format and ensuring you make no spelling mistakes, you will guarantee your website-based app has a professional, unique identity on the Google Play Store.

CW

About ConvertWebsites Editorial & Engineering

Our technical tutorials and guides are authored and maintained by the ConvertWebsitesToApp engineering staff. Every guide is tested against modern Android SDK guidelines, Google Play Developer policies, and Chromium WebView standards.

Learn About Our Team → Suggest an Edit / Topic →

Ready to convert your website into an Android app?

Generate a production-ready, signed Android APK with push notifications and AdMob in under 60 seconds.

Generate APK Free Online

Recommended Guides & Tutorials

How to Install a Website-Based APK on Android

A quick tutorial on how to install a website-based APK file on your Android device by safely bypassing the 'Unknown Sources' security prompt.

Read Guide →

How to Handle External Links in a Website-Based App

Don't trap your users! Learn how to properly configure external links in a website-based Android app so they open in the user's native browser.

Read Guide →

How to Update a Website-Based Android App

Discover the massive advantage of website-based apps: effortless updates. Learn how content updates work versus structural app updates.

Read Guide →