Visual Studio Marketplace – Publisher Pivot

Visual Studio Marketplace is the exclusive destination for discovering extensions for Visual Studio IDE, Team Services and Code, and purchasing subscriptions. While consumers of the Marketplace benefit greatly from it, we want our publishers to have a great experience too. After all, it is they who make the Marketplace rich with real world extensions and integrations.

This post gives you a sneak peek at the set of publisher centric enhancements that we plan to bring to Marketplace in Q2 CY 2017. As always, the timelines and designs shared in this post are subject to change.

Publisher Hub

As the publisher of a VSTS extension, you want to know how your extension in performing. Publisher Hub would provide you all such context and more:

  • Insights about how your extension is being acquired, such as uptake around VSTS & TFS, conversion funnel from impressions to page views to installs
  • Information w.r.t. uninstalls of the extension along with related reasoning
  • Be able to analyze how the extension is being reviewed/rated & then drive actions right from this hub
  • And also, be able to download this data for your offline processing as need be

Hub

We are likely to enable this for paid extensions first.

Support for Extension Versions

Our publishers shared the following cases with us:

  • We wish to test the v2 of my extension while its v1 is being used by customers in production
  • I wish to patch my extension and try it out with a limited set of customers before sharing it more widely

For both above, a versioning story becomes essential where the in-development extension can be privately shared with selective account(s) to solicit feedback and aid testing. Hence we plan to enable a versioning story for extensions (Team Services and TFS only) in coming months. Likely on the following lines:

version

Q&A Support

User reviews on the extensions today is being overloaded by consumers for questions and support as opposed to just reviews. Since rating is mandatory in such situation, this can negatively affect the extension rating overall and in turn the publisher. Hence a Q&A section is being added to support dialogue between publishers and their consumers across all extension targets. Appropriate notifications would be sent when a question is posted or answered. qa