We’ve Updated the Adobe XD Plugin Workflow on the I/O Developer Console

Updated Tuesday, March 7th: Check out our follow-up article with more details about the new plugin manifest.

This week’s guest post is by Courtney George, an Experience Design Manager for the Adobe Design Developer Ecosystem team.
Do you have an XD plugin in the XD Plugin Manager? Are you about to update your plugin, or submit a plugin for the first time? If so, this article is for you.
Erin Finnegan, Community Engineer, Adobe

Improving the plugin submission process

Since we launched XD plugins on the I/O Developer Console last year, we’ve been listening to feedback from developers like yourselves. We have been steadily working since then to improve the plugin submission and review process.

Our Adobe Design Developer Ecosystem team has been working with our product and engineering stakeholder teams to improve on the experience we built last year by making it easier for developers to create plugins and publish them to the XD Plugin Manager.

What’s changed

We’ve made a few key changes to the experience:

Decoupling the project name and the public plugin name

Currently when you create a plugin you’re required to pick a unique name that users will see when you publish your plugin. This created some friction for developers since you had to think about the public-facing name before building your plugin and you couldn’t rename your plugin after creation.

With this new release, we’ve improved that experience and now you can create a plugin project name that is independent from the public-facing name that users see in the XD Plugin Manager. This project name needs to be unique to you as an individual, but it means every developer can have, for example, their own “Test” plugin project name, which was something that we heard during user testing. This project name can also be easily renamed within the Console experience.

New submission flow and new manifest features

The biggest change to the experience comes in the submission workflow. We heard that many developers were testing how their listing information would show up in the Plugin Manager during development.

So, instead of inputting that information in the manifest file and then once again in a web form during submission, we now only require that it be a part of the manifest file.

When you’re ready to publish your plugin, all you’ll need to do is upload your .xdx file and review the listing information we extract directly from the manifest file. As part of this, we now offer immediate validation of your manifest, which will result in a much quicker feedback loop for manifest errors.

We’ve also included some new requirements to the manifest file like a summary and keywords, that will help with discoverability of your plugin in the XD Plugin Manager.

Published status

The plugin details page now changes to provide more relevant links after a plugin is published. We now surface links to join the Adobe Exchange Program for Creative Cloud and for resources to better market and promote your plugin.

Update your manifest today

All of these changes are live today in the I/O Developer Console.

If you’re totally new to plugins, just follow along the docs. We’ve updated them with everything you need to know. If you’re in the process of developing a plugin or plan to update a published plugin, you’ll need to update your manifest to meet the new requirements for submission.

You can learn everything you need to know in our manifest reference.

The changes to your manifest are in preparation for the XD plugin manager updates that will go live later this year. The developer workflows are live now so you have time to make those updates before end-users see the updated plugin manager.

If you would like to see the updates to the plugin manager ahead of time, you can join the Adobe XD prerelease program.

We invite you to check out the new XD plugin experience on the I/O Developer Console today! If you are stuck and haven’t submitted yet, please ask any questions in the developer forums.

Don’t forget: Check out our follow-up article with more details about the new plugin manifest.