Keyboard ALT + g to toggle grid overlay
This guide is for developers and content providers new to publishing add-ins and other content on the Autodesk App Store—either free, trial or for fee-based versions. It outlines best practice guidelines and a few requirements for publishers to follow when creating products for the Autodesk App Store. These guidelines are designed to ensure that users on the Autodesk App Store have a consistent experience when downloading multiple products from the store.
You will be presented with a detailed list of requirements for publishing on the App Store when you first register to be a publisher. The information that follows is a summary. If there are any differences, then the online Publisher Agreement takes precedence.
Most of the information we need from you is collected via the web form you complete when submitting your content. This includes gathering information to create a HTML ‘quick start’ page that is included with the download of your product and viewable online. Other requirements are:
Your product must be relevant to (and usable with) the latest version of Fusion 360.
The documentation information you provide when submitting your app will be used to create a standard format HTML page, and must allow the user to quickly understand how to use your product. You can reference additional information (for example, additional help files posted on your website) from the standard HTML documentation.
We strongly recommend you make use of the standard the Autodesk App Store app installer we create for you. Installers can be created for Windows and Mac depending on which platform(s) you submit your app for. Fusion 360 apps are installed per user in a user specific directory and do not require any additional privileges.
If you use a licensing system then it must allow your product to run as soon as it is installed by the user. This means either instant activation (for example, online activation), or your product must run fully functional for a time-boound grace period that is long enough for you to send activation information to the customer.
There are no additional requirements for products that are not integrated with Fusion 360. Such products might include eBooks, video tutorials, industry specific calculators, and the like.
Minimize add-in start-up time. Fusion add-ins are loaded when Fusion is started so every add-in affects the time it takes for Fusion to become available for the user to begin working. Fusion supports getting some add-in performance information so you can measure the load time of your add-in.
Access to your apps commands should be in a logical location. You are strongly discouraged from creating a new panel in the toolbar but should instead use existing panels or in the case where your functionality doesn’t fit within an existing panel, your command(s) should be added to the Add-Ins panel, as shown below. Users can choose to promote your command(s) to the top level of the toolbar if they use it frequently.
Inside one of the below root folders you need to create a uniquely named folder whose name ends in “. bundle”. Directly inside this folder should be a configuration file named “PackageContents.xml”. There should also be a “Contents” subfolder where you put your deliverables.
So, the minimum ‘development’ installation would have 2 files, and be along the lines of:
The following locations are supported for loading Fusion Apps.
The per-user root folder for Windows version is:
Whilst the per-user root folder for MAC version is:
Apps installed in the per-user folder will only be available for that user.
Every submission of the same app should have updated version number.
The ADN team is here to help you be a successful publisher on Autodesk App Store. We’ll do whatever we can do to help you. If you have any further questions after reviewing these guidelines and the other documentation on www.autodesk.com/developapps, email us at email@example.com.
Thank you for participating on Autodesk App Store.