Fusion publishing guidelines

This guide covers the requirements and best practices for publishing Fusion apps to the Design and Make Marketplace. Follow these guidelines to ensure your app passes review and works reliably for users.

Requirements

When you register as a publisher, you'll see the complete requirements in the Publisher Agreement. This guide summarizes the key points — the agreement takes precedence if anything differs.

All content types

When you submit your app, the form collects everything needed for your listing — including content for the quick-start page that's included with downloads and viewable online.

Additional requirements

Compatibility

Your product must be relevant to (and usable with) the latest version of Fusion®.

User privileges

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 apps are installed per user in a user specific directory and require elevated (admin) user privileges.

Product stability

Your product should be stable and not behave or alter the behavior of Fusion in a way that we deem unsuitable, for example, blocking standard functionality, blocking the functionality of another plug-in, causing data loss, etc.

HTML help page

When you submit your app, the documentation form generates a help page that's included with your download. Make sure your instructions are clear and actionable — users should be able to get started quickly. You can link to additional resources hosted on your website.

Ready to run

If your app uses licensing, it must work immediately after installation:

Activate automatically (e.g., online activation), or
Include a fully functional trial period long enough to deliver activation to the customer.

Stand-alone applications and other content

There are no additional requirements for products that are not integrated with Fusion. Such products might include eBooks, video tutorials, industry specific calculators, and the like.

Guidelines

Add-in loading efficiency

Fusion loads all add-ins at startup, so slow add-ins delay the entire application. Keep your load time under 0.005 seconds.

To measure your add-in's load time:

Set the environment variable APPLOG_FOR_PERFORMANCE=yes
Start Fusion
Check the log file at: %localappdata%\Autodesk\Autodesk Fusion 360\<ID>\logs\AppLogFile<timestamp>.log
Search for "ran script" — each add-in shows its load time and run time

If your add-in loads slower than 0.005 seconds, optimize it. Your run() function should only connect command events — defer loading libraries until the command is executed.

Command access

Place your commands in a logical location. Don't create a new toolbar panel — use existing panels, or add your commands to the Add-Ins panel if they don't fit elsewhere.

Users can promote frequently-used commands to the top level of the toolbar themselves.

Folders

Bundle structure

Your add-in must be in a .bundle folder containing:

PackageContents.xml (configuration file)
A Contents subfolder with your deliverables

Example structure:

Platform	Path
Windows	`%APPDATA%\Autodesk\ApplicationPlugins\ADSK.MyApp.bundle\Contents\ADSK.MyPlugin.dll`
Mac	`~/Library/Application Support/Autodesk/Application Plugins/ADSK.MyApp.bundle/Contents/ADSK.MyPlugin.dll`

The manifest file goes in the bundle root:

Windows: ...\ADSK.MyApp.bundle\ADSK.MyPlugin.Manifest
Mac: .../ADSK.MyApp.bundle/ADSK.MyPlugin.Manifest

Supported locations

Per-user install locations:

Platform	Path
Windows	`%APPDATA%\Autodesk\Application Plugins`
Mac	`~/Library/Application Support/Autodesk/Application Plugins`

Apps installed in the per-user folder are only available to that user.

Note: Each submission must have an updated version number.

Get help with publishing

Questions? Email appsubmissions@autodesk.com for support.

For more resources, visit the API documentation and the Developer Community Blog.