WordPress plugins: 1,000 sales in 5 months, 4 days!
I would like to use the opportunity to thank our fellow authors and clients for supporting our premium WordPress plugins! We would also like to thank Envato for creating this great community.
In the beginning of September we discovered that Codecanyon launched the WordPress plugin category. We have worked with WordPress for several years creating premium custom solutions for our clients. However we have never sold our plugins in any market place. We decided to give this a try and developed the first plugin for sale called “Custom Backgrounds for WordPress”.
We made our first sale on September 1, 2010 and now 5 months, 4 days and 8 plugins later we have been fortunate to reach 1,000 sales. :bigsmile
This has truly surpassed our expectations! And we believe that we can do even better.
We will continue to support our fellow authors, by buying quality items for our web design projects. And we will continue to develop premium WordPress plugins that makes life easier for other developers, designers or novice users of WordPress.
We have several great updates and new plugins on the way! Stay tuned. And once again thank you so much for the support.
Hope this is an inspiration to other authors to continue to develop great stuff and provide good support for what you develop.
I don’t think this is 100% clear, but if you look at Themeforest you have to buy an Extended License in order to use the theme on a WordPress MultiSite (former MU). So the same must apply to WordPress plugins – if you want to use it on a WP MS network then you must buy an Extended License.
The Extended License also lets you incorporate (implement) the plugin or script from Codecanyon into another product and resell it. However you cannot resell the plugin/script its self.
1. Top level Category or SubcategoryDefinitely a sub-category for each main category where its relevant.
WordPress Plugins > Add-ons Joomla Plugins > Add-ons
2. Can Others Create Add-Ons for your Item?
This is a very interesting one. So what if someone makes the same Add-On as you wanted to create. As its a Add-on potential customers would still have to buy the main plugin and you would benefit from other authors creating great add-ons.
I personally wouldn’t want an author to OWN the rights to also do Add-ons. The idea is to share and together build something even greater/better.
However I agree with the comment that mordauk made about the original author has to accept (maybe opt-in) that Add-ons are allowed from other authors.
But wouldn’t it regulate its self? I mean if you create an API that allows for add-ons you kinda opened the ball your self. If you don’t create an API for creating add-ons, its probably because you don’t want other authors to create add-ons.
It is also about trimming and slimming your plugins. If you can create add-ons and remove original features then you don’t end up with a plugin which has 250 features. Maybe you are only interested in 10 features.
Some new features would be natural improvements of the original plugin and should not be submitted as add-ons. And others might be so special that not all users would like them to be included in the original plugin.
4. Short-term solutionIf anyone is interested in creating add-ons for our Styles with Shortcodes feel free to contact me.
We have added a banner on one of our add-ons “Alerting” customers that they need the main plugin too.
Our other add-on is awaiting approval, and I don’t want to disrupt that process.
Congratulations with your achievement. You have a great portfolio of scripts, plugins and themes. Keep up the great work!
Several of our plugins (WordPress) are already available in several languages. We have had people contacting us and offering their help to translate. As they want to promote the plugins in their local markets. They believe that it will help them in attracting potential buyers.
I guess its a little bit harder when its not a WordPress plugin as you will have to develop the localization files your self.
You are definitely making a good point. Add-ons cannot require any modifications of the main plugin. It must just be as simply as uploading the add-on plugin and then activating it.
In our case we have made a complete API and easy to use interface to create add-ons. Even a admin script for developers that automatically creates the add on files after creating the Shortcode in the “builder”. All you need to do is upload an click Activate.
The question that everyone seams to be concerned about is who should provide support for the add-on. I personally believe that it should be the author that develops it and that get the profit from selling it.
However as a author of a plugin which allows others to develop add-ons, I’m also interested in that the add-ons work.
Also we cannot just change the API in the main plugin as that would cause many add-ons to not work properly. All this needs to be thought through properly, but I still believe there is a great benefit from Authors collaborating on creating add-ons for Plugins (maybe also themes) that have the proper API (allow it).
I think there are many interesting aspects of this topic. I’ve seen both good arguments against it and for it.
I might be prejudiced because we already created a plugin, which allows theme authors on Themeforest to implement the plugin into their theme and then offer new flexibility for add-ons to their theme. And it allows authors on Codecanyon to create add-ons for the main plugin.
We currently work with two theme authors on Themeforest, one who already purchased an extended license and the other will soon – to incorporate the plugin into their theme.
They will then add their own Shortocdes and we will also be able to develop add-on (new features) that easily can be added, because of the main plugin that is incorporated. We simple “white-label” it so our name won’t occur under plugins or it won’t show up under plugins, but its a core feature. Only in the readme.txt would it be mentioned that an Extended license has been acquired for our plugin to incorporate certain functionality.
I hear some authors saying they don’t want other authors to build add-ons unless they agree on it. I don’t see the big problem. We build our plugin because we wanted other authors to take advantage of this and build add-ons.
If you don’t want other authors to build add-ons to your plugin then you simply don’t offer a API that would allow it.
Of course there is also the question about support. My opinion is that the developer of the plugin (add-on) should support their own work. Of course as the author of the main plugin I’m interested in seeing the add-on work.
I another thread someone suggested that we could offer support subscriptions. There are many possibilities.
Great to see so many authors engaged in this. We all want to see the Envato market places become even better than they already are.
Is the item being stolen from a Envato Market place and sold somewhere else ?
Take a look at these articles http://wiki.envato.com/support/what-to-do-if-you-have-found-your-marketplace-files-being-distributed-or-used-illegally/http://wiki.envato.com/selling/copyright-selling/copyright-policy/
I’ve worked with WordPress for several years and recently started developing premium WordPress plugin on Codecanyon. When you say WordPress plugin usually its a script (plugin) that is installed under plugins and then it has some settings in the wp-admin. Some plugins have their own entire menu and sub-menus with lots of settings and other just have a simply configuration panel (settings).
Common for them would be that they can easily be used in WordPress from the wp-admin when you compose your Posts or Pages. Or configure the content of your widgets, menu’s etc.
I haven’t seen any plugins where you will have to access a external website if that is what you had in mind.
I don’t know if this made any sense, but if you give an example of what you had in mind it might be easier to provide some real advise
Hi Jeffrey, Great idea!
I’ve been an exclusive author since March 2009.
I have a few items I would like to offer the following:
Styles with Shortcodes for WordPress
Launched: November 29, 2010
Rating: 5 Star
URL : http://codecanyon.net/item/styles-with-shortcodes-for-wordpress/142221
White Label Branding for WordPress
Launched: September 17, 2010
Rating: 5 Star
URL : http://codecanyon.net/item/white-label-branding-for-wordpress/125617
These items can be found in my Portfolio: http://codecanyon.net/user/lawley/portfolio
We already offer first class support, so that should not be a challenge.