CodeKit uses GitHub for issue tracking, try checking here: https://github.com/bdkjones/CodeKit/issues?state=open
LOL — home page is 4.4 megabytes
It’s polished alright, but that’ll take 24 seconds to load on an average 3G connection. Who’s actually going to use it?
Comments are probably not clearable individually because Encato doesn’t store a state for each comment. Per user there is a DB field for “last marked as read”. Whether comments are new or not is based off this date. If I recall this was done to speed up implementing this feature 2 years ago.
I do not like when I answer the comment and once the page is reloaded it disappears .
Yes, please change this. I always like to re-read what I wrote and make edits if needed. This isn’t possible when the comment is cleared automatically.
Thanks Christian, when the Dev Team has implemented it can you reply here so I know when those fields can be selected on my item? I’ve subscribed to this thread.
Either continue serving your client by managing updates for them, or have your client purchase the item and hand you the .zip to develop from. There is no way for you to buy and then have an author verify your client when they want to update independent of you.
Thanks Christian, please update this thread when you hear back. I don’t have a ticket open.
I should clarify that I don’t think Envato intentionally chose to shaft authors in this instance, but the design decision that was made effectively does this. That’s why it’s upsetting to encounter because the edge cases were either not considered or deliberately create a negative situation.
@ Vlajki — Say “drama” all you want. Years of experience has proven if these issues aren’t aired in the open forums, they won’t be addressed. I think it’s always better to raise issues publicly so others can comment and express an opinion.
Please make the next/previous buttons wider (add a text label) in the forum pages and lists. As someone who reads / comments on the forums exclusively from an iPhone, navigating between posts is the most annoying thing before the marketplaces are made fully responsive.
Finally, no more brown.
(1) (2) (3) All have the same answer: Success means the Envato marketplaces support sustainable business.
I’ve been here four years, and the marketplaces have exploded in item and user volume. More users = more potential buyers. But more items = less exposure per item.
Some authors are thriving (a few like Scrooge McDuck) by riding the popular lists for month after month (I was one of them). But many are increasingly frustrated and (unrealistically) still banking on an exposure-driven business.
Envato’s business model only supports Envato during massive scaling. Envato earns regardless and individual authors compete for less. It doesn’t matter if authors drop like flies, they are replaceable.
I shake my head whenever an author suggests redesigning the homepage will solve all the problems that scaling brings. There is no equitable design solution for exposure when 30+ items are approved daily. The model has to fundamentally change.
For Envato to be a sustainable marketplace, the value of author support must be recognized monetarily. Envato’s competitors have done it. There was hand wringing and ALL CAPS for a while, but ultimately their customers (the paying ones — not the other kind) stayed because they valued support services.
Churning out new items is less and less sustainable as it becomes the norm. Stop ignoring real value: having the original developer on-hand for support and continued item updates. Getting paid for those things means authors won’t rely their few hours of homepage exposure so much. They just need a few customers and to keep them happy. Happy customers are a tumbleweed of sustainable profit.