Create a Submission
Submissions represent versions of your product page that you would like to publish on MuseHub. They contain your product metadata, assets like binaries and promotional images, release notes and more.
Submissions in MuseHub represent a snapshot of the metadata and binaries associated with a product. Once submitted to Release or Beta status, the metadata becomes read-only, and cannot be changed without creating a new submission.
Duplicate a submission using the duplicate icon in the submission row to avoid having to start again each time.
Submission type
Beta: This will make the product accessible within the Hub to beta testers that you've invited to the product beta, via the Beta Testing tab.
Release: This will submit the version to Content Review, before releasing the product to the full MuseHub audience.
What's new?: Fill in your release notes here, highlighting any new features or important changes since the last release.
Description: This is a long-form description which should continue on from your Short Description, used to inform customers about your app's abilities and features. There is no limit on this text field, but short and punch descriptions work best. Don't duplicate the "Short Description", since these are shown together
EULA (optional): If you have a custom EULA, then enter or copy it in here. If you leave this blank, the Hub will show the MuseHub Standard EULA, as outlined in the MuseHub Distribution Agreement.
User Guide (optional): (.PDF) of your user guide which will be downloaded and shown to users if they click the respective button on your product page. The user guide is accessible to all MuseHub users.
Knowledgebase Document (optional): a .txt or .rtf file, used by our internal systems and customer support agents to help support a customer through the use of automated systems (AI knowledge retrieval) or human reference.
Features: Highlight the top-selling points of your product here. Display them in blocks of 3, 6, or 9. Keep each feature brief, ideally between 70-100 characters.
Previews: You can add up to six assets to demonstrate your application. Please ensure these adhere to the Content Guidelines.
Audio (.mp3, .m4a): This could be a song or demo track, or an example of the sounds you can create with your application. You can give this a title, and a waveform will be automatically geneated.
Image (.jpg or .png): A screenshot or product image showing your product in use.
Video (.mov or .mp4): A video file, such as a walkthrough or product trailer, that shows the product in use.
Assets: Drag your supported asset type (.zip, .dmg, .pkg, .exe, .MSI, .MSIX) here. These should be the installers or binaries for the product that you are distributing. After uploading, you can select the platform architecture using the dropdown menu, such as separate Apple Silicon or Intel installers. MuseHub will automatically install the correct architecture based on the customer's device.
OS: If you've uploaded an installer, check that this field corresponds to the target OS for the installer. This is also where you can specify an Intel vs Apple Silicon installer, for macOS.
Version : This must be a three-digit format: N.N.N (e.g. 1.0.0). Ideally, align it with the actual application version, but it's not mandatory. Increment the version number with each submission.
Enable DRM: If you are submitting a paid commercial Application, it should have Muse DRM applied or the Muse SDK integrated. Turn this switch on to reveal the DRM Processing ID fields. You should copy in each Muse DRM Processing ID generated by the Muse DRM tool to the corresponding asset or installer.
MacOS Properties:
Bundle ID: If your applicatoin is a macOS .app, then MuseHub can optionally also act as an application launcher. For this to work, you need to fill in the bundle name, from your applications info.plist. Example:
com.muse.hub
Minimum OS Version: MuseHub supported macOS back to macOS 11 Big Sur. If your application has a different minimum required version, you can enter it here to prevent it from being installed on incompatible versions of macOS.
Windows Properties:
Application ID: Many Windows installers use an App ID or Installer Upgrade Code to help Windows track installations. MuseHub uses this App ID/Code to automatically launch the application and ensure reliable updates by choosing the best method. Set this installer code or App ID when creating your application's installer. Enter it here for maximum compatibility with MuseHub's installer system. Without your Application ID, MuseHub cannot reliably launch or uninstall your application.
Minimum OS Version: MuseHub supports a minimum OS of Windows 10 21H1. If your product has a different minimum version of Windows required to run, you can enter it here to ensure it isn't installed on incompatible versions of Windows.
Once you've finished filling out your version details, press "Save".
Last updated