Perceptive Automation and 3rd Party Developers
With the invention of Indigo server plugins and the creation of the Indigo plugin bundle, several developers have asked about including 3rd party plugins in the Indigo installer and/or if we would be interested in co-promotion of 3rd party plugins. We've also been asked about using Perceptive Automation and Indigo images in 3rd party plugins. This statement will serve as our policy regarding these (and other) questions. Any changes to this statement will be published as change/addendum statements to this thread (for the time being).
3rd Party Plugin Distribution, Support & Sales
The recommended mechanism for distributing plugins is via our plugin store. For information on how to submit your plugins to our online store, see the Plugin Store Submission Guidelines.
Monetizing the 3rd party ecosystem is something that we have considered from the beginning. Polling of the current 3rd party development community, however, shows that a vast majority currently prefer to distribute plugins with no cost. We currently provide developers a way to publicize a PayPal donation URL for their plugins. If you would be interested in being able to formally sell your plugins, then let us know so we can track the demand for such functionality.
We've also created an area in our user forums, 3rd Party Developers, where developers can post announcements and documentation and where they can provide support for their users. If you wish to have your own sub-forum for supporting and announcing your plugins, then follow the steps outlined here.
If you already have your own website for these purposes feel free to skip this step – it's provided merely as a convenience for those developers who don't already have some kind of web presence.
Co-Promotion
We've been approached several times already about doing co-promotion of 3rd party plugins. While we will do everything we can to assist developers in the creation and selling of plugins, we don't feel at the moment that we want to enter into any kind of co-promotion or co-marketing agreements. There may be cases in the future where we would consider doing so, but our primary focus right now is on developing Indigo and extending Indigo's plugin API. We may, however, highlight 3rd party plugins for inclusion in our Newsletter. See the Tweet and Newsletter Mentions section below.
Use of Perceptive Automation Media
Use of any media from the Perceptive Automation web site or from any Perceptive Automation application (Indigo, Indigo Touch, etc.) without prior consent is unauthorized. Permission to use the Perceptive Automation logo or the Indigo logo will likely not be given. Indigo plugin bundles will automatically retain the Indigo plugin image. Developers are authorized to use screen shots of their configuration dialogs and any associated Indigo screens — as long as the shot highlights usage/display of specifics of the plugin. General screen shots of unrelated Indigo windows in marketing materials should be avoided.
We want our 3rd party developers to develop great plugins that will benefit and grow the Indigo community, and we've worked really hard to provide the APIs necessary. We feel that the new Plugin Store and these guidelines will allow all developers to successfully market their plugins to the Indigo community and create a thriving 3rd party ecosystem around Indigo.
Tweet and Newsletter Mentions
In order to help developers get some visibility with the Perceptive Automation customer base, we are going to start tweeting each new 3rd party plugin that becomes available. In order to avoid any kind of bias, we will only tweet a plugin when it becomes available in release quality. The order of tweeting will then be based on the submission date. We'll tweet a small synopsis along with a link to your sub-forum post or plugin store page. If you don't want your plugin mentioned just let us know and we'll skip it.
Following these same rules, we may include 3rd party plugins that have been released in the next Newsletter which we usually send out roughly three times a year. The mention may include expanded descriptions of the plugin but at a minimum will include what was covered in the Tweet. Again, if you don't want your plugin mentioned just let us know.
If you have any questions/comments about these policies please feel free to email us at developer DASH relations AT indigodomo DOT com.
Perceptive Automation and 3rd Party Developers
- jay (support)
- Site Admin
- Posts: 18339
- Joined: Wed Mar 19, 2008 11:52 am
- Location: Austin, Texas
- Contact:
- jay (support)
- Site Admin
- Posts: 18339
- Joined: Wed Mar 19, 2008 11:52 am
- Location: Austin, Texas
- Contact:
Re: Perceptive Automation and 3rd Party Developers
10/20/2011 - added "Tweet Mention" section to the 3rd Party Developer Relations Statement.
- jay (support)
- Site Admin
- Posts: 18339
- Joined: Wed Mar 19, 2008 11:52 am
- Location: Austin, Texas
- Contact:
Re: Perceptive Automation and 3rd Party Developers
11/2/2011 - changed "Tweet Mention" section to "Tweet and Newsletter Mention" in the 3rd Party Developer Relations Statement and added some discussion of what a mention in the Newsletter would look like.
- jay (support)
- Site Admin
- Posts: 18339
- Joined: Wed Mar 19, 2008 11:52 am
- Location: Austin, Texas
- Contact:
Re: Perceptive Automation and 3rd Party Developers
11/3/2011 - changed "3rd Party Plugin Distribution, Support & Sales" section in the 3rd Party Developer Relations Statement to add the steps necessary to create a sub-forum for your company in the new "3rd Party Developers" forum.
- jay (support)
- Site Admin
- Posts: 18339
- Joined: Wed Mar 19, 2008 11:52 am
- Location: Austin, Texas
- Contact:
Re: Perceptive Automation and 3rd Party Developers
3/15/2012 - Modified the requirements for getting mentioned in Tweets and/or Newsletters.