Posts by GDragoN

355 posts
  • Industrious API Inventor
  • Author Level 6
  • Most Wanted Winner
  • Featured Author
+5 more
GDragoN
says

Since alot of support forums by authors here use bbpress, I think it’d make more sense for Envato to build something for Envato’s new API which authors can use to verify support validity. For now, I’d rather provide support even after 6 months than build a new plugin to integrate with Envato’s API.

I have plugin that does that and it is available on CodeCanyon. I will release update next week that will take into account support too. Problem will be testing, since Envato has not provided any sandbox to try it with test data, but hopefully, all will go OK.

355 posts
  • Industrious API Inventor
  • Author Level 6
  • Most Wanted Winner
  • Featured Author
+5 more
GDragoN
says

Based on your description it is too simple to be accepted. Also, 12Kb for such plugin is too much, you can make element fit window with one function and few lines of code, or some more if you use animations to expand the element to fit.

355 posts
  • Industrious API Inventor
  • Author Level 6
  • Most Wanted Winner
  • Featured Author
+5 more
GDragoN
says

I’ve got a question regarding API’s: what if I stop supporting an item?
Do users, purchasing the item after that moment, have a sort of flag to avoid registration on our systems?

For example: currently I check the purchase code and I’m going to check the support period for that user. Will I be able to know if that user purchased the item after I opted-out?

Hope this is clear :)

I think that every item will have support activity date, but if item is not supported it will be null. I would like to get confirmation on this too.

355 posts
  • Industrious API Inventor
  • Author Level 6
  • Most Wanted Winner
  • Featured Author
+5 more
GDragoN
says

Is there a list of planned API changes? It’s a bit hard to ‘get ready’ when we have no documentation on what API changes are coming. An API sandbox would have been perfect in this case.

API is still not expanded, and I will not hold my breath about sandbox for that. Hopefully, lets get the API methods on time. Such changes would require at least 1 month in advance availability and testing methods, right now that is all not done.

355 posts
  • Industrious API Inventor
  • Author Level 6
  • Most Wanted Winner
  • Featured Author
+5 more
GDragoN
says

I was proposing the same thing. But, you know what “Envato has already discussed with 10 experienced authors” and this is their best strategy to deal with support.

Can you believe it?

In the past few months I talked to some of my buyers and to many professionals in the field, and no one can believe how Envato can propose and go ahead with such plan. I would really like to talk to these ‘experienced authors’ so they can explain the logic behind this.

355 posts
  • Industrious API Inventor
  • Author Level 6
  • Most Wanted Winner
  • Featured Author
+5 more
GDragoN
says

... Do i receive help in such a case only if i own a support pack? That would not be logical.

This whole idea has no logic to it, and it will create mess in the coming months. Envato only takes money for selling support packs, and washes hands from any responsibility, authors will need to enforce support rules that have too many holes that will be open to all sorts interpretations, buyers will be angry for the need to pay for support because they will get updates but no support for them after initial 6 months expire, and they are foced to pay for that support. Support channels are all open for interpretations and authors will be ‘bad guys’ for telling buyers to buy support first.

In the end, Envato will earn some money with no responsibilities, buyer will be angry about all this making less purchases, giving bad ratings, authors will be left on their own to deal with the mess.

The only way for this to work is:

1. Envato provides support platform, and ONLY that platform can be used for support. This way they can control who has the right to access support and when. In that case 30% they take will be valid and earned.

2. Comments for items need to be merged into this support platform for buyers with license, comments can be used only for presale questions from now on.

3. Authors need to shut down own support forums, and redirect everything to official Envato based support.

4. Envato needs to have dedicated team to monitor ratings buyers leave, and to monitor support platform to make sure buyers and authors don’t abuse the system.

This is the only way to make this system work, if Envato wants this to work, Envato needs to have full control over the process, authors can’t be responsible to enforce the rules that are open to implementations and badly formulated.

Milan

355 posts
  • Industrious API Inventor
  • Author Level 6
  • Most Wanted Winner
  • Featured Author
+5 more
GDragoN
says
355 posts
  • Industrious API Inventor
  • Author Level 6
  • Most Wanted Winner
  • Featured Author
+5 more
GDragoN
says

What I want to know is what is the situation with the Request Staff Reply link?

I have used it now and 3 times in the past and have never received a staff response! Is it only optional or what?

Things sure have changed. I remember times when Collis personally responded to my tweets and messages and now I cannot get an answer from the staff. I guess I will send my questions through a ticket maybe i can get an answer that way.

I too used Request Staff Reply 4 times in past 4 days, and still got no replies. Past week all we get are generic same replies they are sticking to from the start, no actual question was answered directly, all is copy / paste responses.

I have not see Collis here for months, since the VAT introduction. So much for his ‘direct involvement’ in running the Envato and working with authors.

355 posts
  • Industrious API Inventor
  • Author Level 6
  • Most Wanted Winner
  • Featured Author
+5 more
GDragoN
says


I’m sorry to say this, because I love Envato Market, but when things become complicated and difficult and heavy, they tend to fall apart. I’m not a dreamer, I’m not 20 years old anymore and I’m realistic. I’m 38 years old and the same happened to the successful company where I worked. The same happened to a lot of things around me. They thought they will improve things, but what they did was in fact to complicate more and to go down. I really really hope this is not going to happen.
I guess we should now just forget this thread and see how buyers react on 1st september.

I will tell you how they will react, considering I talked with about 30 of my customers: we the authors should be happy if sales don’t go down, I doubt we will see any sales or earnings increase at all.

Most of the buyers I talked with are confused about what they are buying and why, considering that they mostly purchased items from authors that supported items for free, and these buyers don’t like the fact that they need to pay for something they get free under the author terms. 20 (out of 30) buyers said that they will purchase less items than before if they are forced to buy support too. They don’t like idea about paid updates most authors want (Envato doesn’t), but they can understand why it is better for them to have something like that, because most of them had purchased items that were abandoned after some time by the authors.

I expect that sales will remain as they are now, and maybe they will fall more then they have been falling since March. I will switch of support for all my cheap items, I don’t plan to tie myself into 6 months support for $1.00 per item and hope that buyers will understand that they can get support as before on my official support forum.

355 posts
  • Industrious API Inventor
  • Author Level 6
  • Most Wanted Winner
  • Featured Author
+5 more
GDragoN
says

Late fees must be specified in the contract, and it has to go both ways: you being late in delivery, and client being late in payment. Last time I worked on contract, we used 10% price cut for each week of late delivery, and 5% price increase in each week of late payment.

by
by
by
by
by
by