I like these posts. I just posted one myself : )
It is motivating to be congratulated on achieving a milestone, regardless of what that milestone is, as long as it represents something to the person posting. Perhaps Envato could start a “Milestones” forum or something similar?
Since many of us probably spend much of our time working alone, connecting with fellow designers here is one opportunity to hang out with peers and share our collective experience.
When l made my first sale l thought, oh, yeah, it was at the top of the listings, and when it goes off the first page results, sales will disappear?
How wrong l was.
Made another sale today, so obviously keywords, etc do help!
Getting stoked to finish off my next project, or redo it. And see how that goes.
It seems that if you keep the quality high, sales will take care of themselves!Shane :0}
Thanks, Shane! One of the great things about this marketplace is that our stuff is always available to the world. Looking forward to your next product.
That’s an awesome script! I haven’t experimented with custom shapes in PS much yet, but I can see how this would save a ton of time.
Wow, great set of tips! I hadn’t heard of #4 either. Thanks for posting these.
Congrats! Here’s to the next 1000 : )
I agree that inclusion of the “Customization” and “Support” options may lead buyers to think those are definitely part of the purchase agreement. I have a suggestion which, while larger in scope than the current implementation, may solve this dilemma in the future. (If you’ve already thought of this, then just consider this an affirmative vote for this approach.)
Since these two options are defined at the product level, add checkboxes to the product profiles to be set by the seller at the time the item is created. Then, during the rating process, the code which populates the Reason dropdown list would look at these product attributes and include them in the list only if they were set to True. This would eliminate potential misunderstandings for customers while adding clarity to the purchasing agreement on the front end.
I understand, being a programmer myself, that the above suggestion is not a simple or quick fix. But perhaps in the long run this will allow for better communication through the product lifecycle and a better experience for all.
Thanks for listening, and thanks for working to improve the system.