There are quite a few authors that work for Envato, many of which have been personal inspiration. However, working for the company makes voicing your author-related opinions and concerns a little more difficult. As with any forum, people easily misinterpret things – and this could lead to a bad representation of the company. So, for the most part I remain silent on such matters. However, this situation is concerning to many authors, which is why I replied.
Right now is a good time for the community to speak up and post ideas for handling this.
Hey GravityDept, You have solid points, and the bottom line is that no system will be perfect for everyone. Before I go any further I need to clarify that I’m not representing Envato – but speaking as a seller.
With my suggestion I didn’t mean for all authors to stop providing updates or support on their items. I even mentioned that there would continue to be many serious authors like yourself that stand behind their items. The idea is to maintain our ability to deny support. I’ve always provided support on all of my items – and have always gone to great lengths when writing documentation as well. There are very valid reasons to deny support – which I’ve outlined in all of my docs as well. Some of these include suspected piracy of Envato items, rude buyers and requesting support outside of 6 months. For me, this is the most appropriate and “fair” way that I can manage support on my items… but it won’t work for everyone.
A lot of people are here because they want to sell GOODS, not SERVICES – which I think is where things really start to break down. You’re partially right about taking your car to a junk garage – they might screw things up. But Envato Studio – contrary to a junk garage – is full of professionals very much capable of coding through TF or CC items. While the author may be the best person to provide support for an item – there’s a whole community of other viable options, waiting to make a few bucks on the work that some authors don’t want to do.
So, while authors remain doing what they’re doing now – rather than expanding all of the marketplaces with special support requirements that would lock some into situations they’ve been trying to avoid in the first place – why not isolate item support to Envato Studio? It would fuel the community in a new way, allow authors to continue doing what they love and servicing their products how they see fit, and provide a new sense of support for buyers. This would also provide a more flexible support avenue in some instances such as buyer/author language barriers.
My main point of my previous post was that I was drawn here to sell PRODUCTS – which then lead into support and maintaining those products. Pretty sure we all came here for the first reason, and pretty sure not everyone agrees on the second.
What initially attracted me to the market was selling a product made once, multiple times. The implied idea behind that being only having to do the work once. I think it’s safe to say that many others were attracted for the same reason. Then updates and support comes in and suddenly that ‘work once’ model turns into an ongoing job – changing that model. Handling Updates and Support for an item brings up a handful of issues that are only indirectly related to the product itself. The warranty for a car shouldn’t necessarily be a reflection of the car itself. I think we need a solid distinction between services and goods. I started here to sell products, and get away from servicing clients. However, there’s a whole sister market for services with many capable developers that would probably love to make an income customizing and supporting plugins and themes. Seems like everyone would win and any support / update issues would at least be isolated to a single section of one market. Serious authors will continue to write clean code and keep their items current. [ speaking as an author ]