Pick the name that most represents your app and use lowercase. As an example, a snap of the Firefox web browser should be called “firefox”. Do not prefix or suffix the name, for instance with your username or “-snap.”
Snap names are globally unique and cannot be changed. For example, only one snap can be named “firefox” and it can never be renamed. Ultimately, each name should be owned and published by members of the relevant project. For example, the snap named “firefox” should be owned and published by the developers of Firefox: the Mozilla project. However, if you are not associated with the project but want to help them create a snap, we welcome you to join snapcrafters, create the snap yourself, register the name and hand off to upstream projects when asked.
To register a name, log into your developer account and click “Register snap.”
If the name you want is already in use and you believe you are the rightful owner, you can register a dispute. Follow the on-screen instructions to be guided through this process. Your dispute will be reviewed by a member of the Snap Store team and a decision communicated by email.
Make sure that the name you registered is the same as the
name field in the
snapcraft.yaml file of your snap. You’ll need to rebuild your snap after you changed the name, a quick process when only the snap name has changed.
There is a single exception for having your username as a suffix in a snap name: an unofficial snap that has no chance of being handed over to the official project.
This should be done with extreme caution because we don’t want to end up in a situation where, for example, “firefox-john” gets super popular and the developer decides they want to call it “firefox”. This is not possible because snaps cannot be renamed. So it will be “firefox-john” for ever, or they upload a second “firefox” snap and you end up orphaning the “firefox-john” snap and those users will not get updates.
See Releasing your snap to learn how to upload your app to the Snap Store.