ive bought all your items from the cc marketplaceyou do execellent work, i would love to know your rates.
feel free to contact me through my personal profile and we can talk about it. It all depends on the scope of the project and what type of project.
I would also be in both categories.
However I talking about this from producing WordPress plugins where they user only needs to “activate” the plugin and then do no more.
So I guess the two situations are quite different. With a WordPress plugin if it solves the same purpose I would always just create an upgrade.
I hope I didn’t just repeat my self, but made it more clear
Some of my plugins are already in version 2.0.2 and have had major changes since the beginning. However I have not launched a new version which the client needed to pay for again in order to get the new features.
Unless the plugin suddenly does satisfy a totally different need then I would not launch a new version and charge money again. We specialize in WordPress plugins and there are thousands of free plugins for WordPress, so if you want to create something that you expect client to pay for you need to support your plugin.
A happy customer will gladly buy from you again. A unhappy customer will never buy from you again. That is my philosophy when it comes to plugin development.
Personally I would do a version 2 etc… If the script still solves the same “problem” or purpose, but maybe just adds more features then I would definitely release it as a big update.
Some of our plugins has been rewritten entirely as we have discovered that they have become quite successful. The interface has been improved, but that is pretty much the only thing that is visible to the user. The rest is “under the hood” if you know what I mean.
Personally I would be annoyed if I purchased a great plugin just to find out that the author then launches a new plugin that does the same, but might have some new features. Then the development of the original plugin stops and only the new will be updated. That would force me to purchase the new plugin if I want the new features.
I see where you come from it would be nice to release another successful plugin, but I think your long term success will be bigger by improving something that is already a success or making something better.
Just my point
I think the addon category would be a nice idea,
- I don’t really think, that the author of an addon should have the rights of the corresponding item, ‘cause if a buyer needs some modifications/addons he would hire a freelancer or… and have to pay much more – so the author of an addon could be the owner of the item or another one
my thoughtskind rgds
I totally agree with you. Any author who creates a ADD -ON to an already existing plugin should be the one responsible to providing support. He/she who created the ADD -ON is also the one who gets paid.
Let me give you an example If you would create a really cool add on Shortcode for our Styles with Shortcodes and then sell it on Codecanyon as a ADD -ON and it becomes popular. I would of course be very interested in making sure it would work with my plugin. And I would be willing to help you make sure it works as your sales would benefit me in the end – as you need my plugin in order to make your ADD -ON work.
That is how I see this would benefit both of us. And it would create some great collaborations between exiting authors.
There are so many skilled authors on Codecanyon who could be able to come with up great idea for ADD -ONs, so personally I would encourage them to use a mutual platform for distributing them.
Does this make sense ?
This is what I have been waiting for
We have developed a plugin called Styles with Shortcodes for WordPress, which at the moment contains 78 built in short codes. The plugin also allows other developers to develop ADD -ON’s (new Shortcodes) and then sell them on Codecanyon.
We have developed one ADD -ON, which is called SWS : Nivo Zoom & Slider and I specifically asked to have it priced low (like $3-$6) as you need the Styles with Shortcodes to take advantage of the ADD -ON.
The idea with developing the Styles with Shortcodes was that we wanted a platform or (API) that would allow anyone with some HTML , CSS knowledge to make cool styling, features etc. for WordPress.
Even though I’ve made sure to write that you need the Styles with Shortcodes to take advantage of the SWS : Nivo Zoom & Slider we did have one customer that purchased the Nivo Zoom & Slider first without buying the Styles with Shortcodes. I explained that it was an ADD -ON to an already existing plugin and it didn’t turn out to be a problem as he got a lot of extra features.
I think that this gives other developers a great opportunity to develop ADD -ONs for already popular plugins.
At this point we have had one Theme developer from Themerforest that wants to integrate the Styles with Shortcodes into his new theme and then anyone who purchases the theme can purchase ADD -ONs and get new styling and ekstra features.
With our Styles with Shortcodes you can export any short code and any other person who has a license for the Styles with Shortcodes plugin can import it. That means you can create small Shortcodes and easily distribute them to other people (either for free or charge a little fee).
I could find several other authors who made cool plugins where I would be interested in creating ADD -ONs for.
The only challenge i see is that the authors of the main plugins would have to develop some kind of API or guide for how ADD -ONs should be created.
Happy New Year everyone!
I’ve been selling the WordPress plugins we develop on Codecanyon since September 1, 2010 and I’ve noticed that a lot of developer or designers who have clients are asking for Developer License for WordPress plugins.
At the moment we have the following licenses when it comes to plugins sold on Codecanyon:
Plugins Regular License Examples
The Regular License could be used for any of the following: Single website (commercial, personal, or non-profit). Single website for a client (commercial, personal, or non-profit). Single intranet site project.
Extended License Examples
The Extended License could be used for any of the following: Component to be used in a template which is then sold (including on CodeCanyon or ActiveDen). Part of a software package for sale.
How much does the Extended License cost for CSS items? The Extended license costs 7 times the cost of the Regular license of the item. For example, a WordPress plugin components that’s $10 under a Regular license, would be $70 (7 x $10) under an Extended license.
Items purchased under a regular or extended license may NOT be redistributed or resold “as-is” or as part of any other collection of image resources or files unless the subcategory’s inherited licensing terms dictate otherwise.
This means that we have to buy a license for each website that we use the plugins on, as the Extended License only lets you incorporate the plugin you have purchased into another product and then sell it. The price for this is very reasonable 7x the regular price.
However this doesn’t help the developer/designer that want to use the plugin on all their customers websites. On Themeforest you pay 50 x the price for being able to get a “developer license” or use the theme an unlimited number of time e.g. on a WP MU installation.
Wouldn’t it be a good idea to introduce a “Developer/Designer” license for the plugins?
I don’t think it should be 50 x the price, but maybe 12-20 times. I’m not sure! What is your opinion on this?
Best wishes for a Happy New Year.