One byproduct of this is developers can ‘hide’ unfinished applications, or snaps which aren’t production quality from users. However, once an application hits the stable channel, users will have expectations for functionality and presentation.
This page details some tips on getting your application ready for the stable snap store channel. Consider it a checklist of best practices for landing in the stable channel.
Snaps in the stable channel must either conform to
strict confinement, or with approval,
classic confinement. In general applications should be using
In the event an application cannot be strictly confined, we recommend starting a thread on the forum to discuss a way forward. If
classic is required, check the process for reviewing classic confined snaps to check if an exception can be made, and then start a request thread on the forum.
When strictly confining your application, ensure you’ve specified all required interfaces. You may have specified interfaces which are not auto-connected. If you believe they should be automatically connected on end-user computers, start a thread on the forum requesting them.
Those will each be discussed and reviewed in the open. In the event they’re approved, a store assertion will be setup so users installing your snap do not need to manually
snap connect those interfaces.
If the snap contains only one binary exposed to the host, and that binary has the same name as the snap, there is nothing to do here. For example the
pulsemixer contains only the
However if you want the snap to expose multiple binaries to the host system, they will by default all be prefixed with the snap name. So a snap called
atom which contains two binaries -
apm will by default expose
atom.apm to the host where the snap is installed.
In this case an alias for
apm was requested for the
atom snap so users can invoke the
apm command via
The snap store supports a single icon for the application, which should be a 256x256 png. The icon can be manually uploaded on the “listing” page of your published snaps or automatically by adding it to the
icon key in
snapcraft.yaml. This icon will show in the snapcraft.io store pages and other graphical store fronts such as the Ubuntu Software Center.
If the application is a graphical desktop app, then the snap should ship with an icon and
.desktop file so that it will appear in the desktop menu. See desktop files for menu integration for more information on how to do this.
The snap store supports uploading multiple screenshots. End users wil see those screenshots in desktop applications such as GNOME Software. We recommend uploading at least one, and up to four screenshots via the dashboard.
An optional banner may be shown in GNOME Software when an application has been selected by the store admins to be featured. The banner should be uploaded in the same place as other screenshots, but must be called
banner.jpg and must be 1218x240 pixels in size.
Uploading a banner does not guarantee the application will be featured, but if it is, the banner will improve the appearance.
If uploaded, the banner icon will be overlayed on top of the banner on the left of the banner image, when displayed in GNOME Software. The banner icon should be uploaded in the same place as other screenshots, but must be called
banner-icon.jpg and its height should be below 240 pixels.
Example banner icon:
How this looks in GNOME Software.
The contents originates in the
description: field, and can be updated via the
snapcraft push-metadata command. In addition, the description can be maintained in the store dashboard.
The support link in the store enables users to provide feedback about your application. It should point to a support site, forum or bug tracker. This field is maintained in the store dashboard General -> Edit -> Contact URL.