^ eventually you’ll run into people who insist you call them on the phone. I remember a funny story with DigitalScience, where a customer somehow was able to track down his personal phone number and called him
^ Here’s how I’d interpret that text:
“Distribute your own items elsewhere” refers to selling them “as is” to someone else. So if you were to literally sell your marketplace item to someone else without any type of customization involved, or if it weren’t part of a larger project, that would not be allowed. But as long as your freelance project involves some type of customization to the item, or it’s part of a larger project (i.e. you’re creating a website for a client and want to include your jQuery plugin as part of the project), that would be allowed.
I’ve had a few inquiries but have only taken one job. The process was pretty smooth. I guess my one gripe is the payment delay. Maybe I’m a unique case, but when I take on freelance work, it’s usually because I need a little bit of extra cash for the month. But because of the current payment window, I’m not really that motivated to take on E-Studio jobs. However, if they paid out within 7-14 days, I’d probably be a lot more interested
I’d like to see little “notifications” when a customer chooses certain options. Here’s an example for “support”, where the support page could clearly state a time-frame for answering questions, which may have avoided a scenario like the one described in the OP.
The same notification would be useful for when someone selects one of the other options, such as “Bugs” or “Customizability”, where the notice could be changed to something like:
“For Bugs or customization concerns, we recommend contacting the author here…”
(if the author has “opted in” to support of course).
I’m sure we’ve all received a bad rating/review from someone who had no idea that support was even available.
My opinion is that the rate reasons should be visible to all, so buyers can see the real rating reasons as well as the small minded ones.
Can’t say I’m a fan of this. Sometimes the 1 star ratings are so ridiculous, they’d really have to include an author reply, because otherwise it’s just erroneous information for the buyer. For example, if a customer rates 1 star with the reason “couldn’t figure out how to accomplish xyz”, yet “xyz” is clearly explained in the documentation, without an author response saying this, it could negatively effect the opinion of future buyers.
.. so an author response would be necessary, but the problem with that is it doesn’t allow buyers to have “the last word”. And having “the last word” is something that’s important to a lot of people (especially unreasonable buyers). Without it, it would just further anger some people, which would probably lead to the customer posting a negative comment in the product’s comments section. Because people who really need “the last word” are going to fight hard to get it.
There’s a long discussion about this here:http://codecanyon.net/forums/thread/any-update-on-multiusedeveloper-or-volume-licenses/54130
@Makis77 My comment was mostly general, as “ratings” threads are fairly common here on the forums. But to reply specifically to your posts:
Ratings should be about certain fields that a plugin covers for example: – Quality – Design – Support – Usability
These options are available to the user when they rate an item. And the options listed are specific to the marketplace. For CodeCanyon, they’re:
- Code Quality
- Design Quality
- Customer Support
- Feature Availability
- Documentation Quality
That pretty much covers everything you mentioned.
where buyers can rate each one of them in a scale 1 to 5. Then the average rating of all those would be the final rating for the plugin.
This is how the rating averages are currently calculated.
Buyers shouldn’t be able to comment ratings, if they want to comment there is a section for that.
This is a feature most authors appreciate. Before, we had no idea why a rating was given. Now, a buyer is forced to leave feedback when they give a low rating, which helps authors capture important information. For example, maybe there’s an obscure bug the author didn’t know about, or maybe there’s a feature missing from the item that’s leading to repeatedly low ratings.
Moreover most of the times buyers cant distinguish if its really a plugin conflict or something else so their comments or reviews don’t give the full picture about a plugin.
This is why I’ve stopped worrying about ratings, as they’re really just a reflection of the user-base’s skill-set. For example:
- Highly competent: 4-5 stars
- Somewhat competent: Depends on their support experience
- Incompetent: 1-2 stars, regardless of support
Yes some items have a large enough bug to warrant a low rating from a competent buyer, but these cases are rare compared to the overall sample.
So to summarize, the reason why almost all items here have an overall 4-5 star rating, is because the majority of customers are highly competent. And the reason why almost all items have some 1-2 individual stars, is because a small percentage of customers fall under the category of “incompetent”. When you look at it this way, you’ll come to the conclusion that it’s pointless to worry about ratings. As long as you’re making a high quality product, and offering support, #1 and #2 above will always outweigh #3.