What the package name is for
Every Android app has a package name — a dotted string like com.yourshop.app — that identifies it to the phone and to Google Play. Two apps with the same package name are, to Android, the same app: installing one over the other is an update if the signatures match and a refusal if they do not. On Play, the package name is the listing's permanent identity; reviews, install counts and the store URL all hang off it. It is set before the first build and can never change afterwards. Change it and you have published a second, unrelated app.
For a website app the natural choice is your domain, reversed, plus a word: yourshop.com becomes com.yourshop.app. That is what this generator does, and what the builder suggests when you make your app.
The rules that fail a build
- At least two segments separated by dots
- Each segment starts with a letter; letters, digits and underscores after that
- Lowercase throughout
- No hyphens —
my-shop.combecomescom.myshop - No Java keywords as a segment:
com.new.appandcom.int.shopfail with a compiler error - Never
com.exampleorcom.test— Play rejects them at upload, after the build succeeded
Paste an existing name into the validator and every violation is named. The generator applies the same rules automatically and shows what it changed — a stripped hyphen, a lowercased letter, a keyword segment given a suffix.
Choosing one you will still like
Use the domain the site will have if a move is planned, not the one it has today. Use the brand, not the product: com.yourshop.app outlives com.yourshop.summersale. Keep it to three segments. You do not have to own the domain for the build to succeed — the convention exists to make names unique without a registry — but if you do not, pick something distinctive rather than com.myapp.app. Then write it down with your signing key; the two together are what let you update the app for as long as it exists. More in the package name guide →