Well, I’m sorry for your item but the answer is about missing features or functionality, not about coding standards. So it seems something related to “what” and not “how”.
Try to work your existing user base a little bit – they will make you money. Setup an email newsletter for that particular item. Setup a facebook page for that item. Get some subscribers. Make your current customers happy and they will be more likely to share your item on social media. Work in an advertising campaign to go with your item update.
A few good reviews, a nice new “updated” item banner and some social media coverage can do wonders.Best of luck with your next major update.
Thanks for the advices. My personal problems with communication to my customer are:
1) I suck doing marketing stuff; 2) I’m not that good with english so I’m always afraid to say something stupid that could ruin my image.
That’s another reason why CodeCanyon is working well for me and for other users, I don’t need to care about those aspects. Anyway, thanks again for the suggestions, I’ll try for my incoming release.
I know this topic was already discussed, I don’t know if my idea was already suggested, though.
I’m going to publish a major release of an item of mine, there will be a lot of new features and improvements that could deserve some attention. But nobody will know it, except my few followers.
Yes, we all know that an “Updated items” section on the home page would be useless, because we, authors, would publish a fix every day to have our items always on that section.
Someone suggested to put only updated items with new features, but there would need a hundred of people to check every update of every item, so it’s clear that can’t be the way.
My idea is: make an “Updated items” on the home page for the recent updated items, but with these rules:
1) publishing an updated item in home page will cost 1 “token”;
2) every author have 4 “tokens” to spend in 12 months, independently by the number of his/her items;
I said 4 tokens but Envato should tune the number of token per year based on their stats. Considering the number of authors and their activity of the last months, to ensure at least one day of presence for each item.
With this system, nobody would care if an update is really a major release or just a small bug fix, you have your precious tokens and you can spend it during an year. What do you think?
I took a small VPS few weeks ago, until now I had no problems.
Europeans are typically on vacations July-August spending money and wen September comes they are short on cash.
Exactly, in Italy August is tipically the vacation month. But I think that’s not a problem of money spent during vacation. Instead I think it’s because usually September is a “start” month, so new projects are being defined and approved and agencies and developers take time to see what their clients want, before buying themes and plugins.
My previous Septembers are both lower than August and October.
these new badges are a step backward, ugly and oldish design.
Yet another thread about the rating system.
I already suggested to have the ability for the authors to reply to ratings. This would be nothing new, Google Play let authors to do it and I think it’s so logical that I’m surprised we can’t do it yet.
My storyFew days ago I received 1 star for an item of mine. The comment of the user was: “The plugin it’s too slow”. Consider that this item got just 4 and 5 stars before that rating. I was going crazy, what the hell does it mean “the plugin is slow”?? How can I contact the user to ask him details about his problem? Probably it’s something stupid, a misconfiguration, but my plugin doesn’t deserve 1 star. Fortunately, the user wrote a comment later to complain about the plugin quality, so I was able to ask him the details I needed to understand the issue and in few minutes (really) the problem was solved and the user changed his rating from 1 to 4 stars.
I know we discussed the rating system so many times but this story is the proof that replies to ratings can be useful for author and users. Would Envato consider this feature?