I’ve often wondered if it’s good practice to say create a new repository for ver 2.0. Obviously it would have significant modifications and enhancements and a decent lifetime run. Would Envato allow this?
If your items will be significantly different, then it is allowed by rules, but my personal opinion that it is bad from marketing point of view. With new “version” you will be able to catch attention of new buyers that are browsing site for new items, but previous customers will be simply left out of the boat.
I really think that this should be solved on the envato’s side with licensing review. There’s nothing bad to ask for license renewal, this is how software business works (renewal or subscription based).
Dave, Thank you for the nice words about our hard work.
Here at WPBakery we think that problem is that envato doesn’t have licenses expiration time, so it’s one time fee for a lifetime updates. I’m sure everyone will agree with me that product should be supported constantly and it cost a lot of human/hours. Keeping records about all purchased licenses and where (domain) they were used is a bit of a problem, but this is the way to say thanks to us (devs) and keep us going and developing it further.
Could anyone recommend a self hosted script/cms for neighbour? Place were a closed community can discuss questions and store some useful (shared) information. Contact list, photos, etc?
Here at WPBakery we know the importance of support and regular updates. If you will take a look at our release history, you will notice that we update our product constantly for the last 3 years in a row and we will continue to do so.
Why Envato is publishing this now if it was already fixed? Obviously it can affect sales… But isn’t relevant anymore (because authors fixed the problem already). I think in that case it would be better if Envato use email instead…
In my personal experience licenses for software are selling in “years” periods. So I think that this should be 1 year of updates and support (access to support forums/ticket system to get help with basic questions not related to customizations and server wise problems).
Then, user should have an option to renew that license in order to receive updates and support (if needed). Most value for users is coming from updates (when project is online). Recurring payments will add another stream of revenue for authors and Envato – as a result buyers will have up to date products (items), because authors will be motivated to continue support of their items.
Overall I think that this is a move in right direction. Many of you already raised questions regarding regulation of support and I agree with them, good point that they are still under discussion.
And I think that I should raise another point: 6 month of support after purchase (with option to upgrade)? – Great!
Lifetime access to the purchased files? Doesn’t sound so great to me… I think that support and source files are actually a single product what buyer purchase, so they should be considered together.
Many great items are showing that success is an outcome from a daily hard work…with constant updates, support and improvements being released. Recurring model for items is the way to go (imho). @Collis please consider that… I hope that author author folks will be with me on this question.