Happy Birthday Envato! New badges look great!
It looks like a pretty well put together system so a solid WordPress plugin might draw in some sales. At the very least you’ll have more experience with WordPress and increase your product offerings.
Depending on demand sales might not be overwhelming immediately, but something like this with good features and integration points would probably do well over time.
I would say give it a shot, see what happens.
What sorts of items are you purchasing (WordPress plugins, PHP script, CSS components, etc)?
I can see if someone was having trouble integrating multiple products into a site that maybe required some development work. Beyond that, are the developers offering support in a timely fashion?
Code quality is always a contentious argument given that everyone is going to have an opinion based on their experience both with a product and with the platform or language that product is built on.
I doubt Envato’s reviewers are just letting stuff fall through the cracks though. If it’s bad enough I imagine they pull products down if they are broken or unsupported to a substantial degree.
Did you check product reviews and comments to make sure what you were buying didn’t have any major issues or that it could perform as you needed?
Usually when I hit a week on review I’m expecting some sort of reject (soft, most of the time). Probably not what happens to everybody, but it’s happened to me a couple of times for various reasons.
It depends on a few things:
- Complexity of the item.
- How many items are in queue for that category.
- How many reviewers are available for that category.
- The schedule of the reviewers.
- Other factors no mere mortal knows about.
I would give it a few more days.
I’m seeing the new homepage as well. Was the old homepage this morning.
Somebody’s been playing with the A/B buttons again.
Second Chance in my pants – Shinedown
The disparity of popularity in items across say, Code Canyon tends to reflect the users of the market items. This is to say that code component items like PHP scripts, CSS items, etc. are more likely to be purchased by someone with development experience.
Consider the probable ratio of developers to non-developers and it’s pretty easy to see why WordPress stands out since it’s an easy to install and use platform and the products for it are also easy to install and configure without advanced knowledge.
A common tactic is to build an item for one category, work out a few bugs, then build additional versions for other categories.
Example: CSS pricing tables can be built as a WordPress plugin or incorporated into a PHP script as an addon or maybe built as a Prestashop module.
WordPress may be king right now, but give it enough time and more platforms will pop up. Part of being a professional developer is adapting to the platforms and languages your customers need and want, not just building stuff you like and hoping it does well.
I actually like not having the # come with the color code. Often times I’m replacing an existing style color and when double-clicking, the editor will highlight the hex value, but not the hash in front of it.
But I suppose it’s a matter of personal preference. Which begs the question: Why not have an option to include it or not?
The help wizard on the other hand is terrible and needs to understand that the most helpful it can possibly be is to get out of my way.
Oh I agree, the main issue being that people are not reading or paying attention to the screen before running into the problem.
My thought is that if we have an article we can link to, it would expedite these types of issues and get people fixed up faster than having to type out the solution every time or having a hundred plus variants of the same process as seller’s write their own articles for this very issue.