Their conversion rates are bad, avoid them if you can.
It’s pretty obvious that themes with multiple demos are essentially bundles. They are running multiple WordPress installations to accommodate that kind of functionality. Multiple installations should be forbidden ( I know it’s hard to force something like that), but if you can’t make all those changes with one installation, then it’s not really one theme that you are selling.
Question to authors: In case of “paid” updates, how would you go about supporting a theme, when not all customers have the same version installed ? Because I’m guessing you would still offer support even if the customer is not on the most recent version of the product? I think that would be a nightmare.
@ graphic4444 Maybe this is a little bit off topic, but here goes. Since you are one of the more serious buyers here, I would like to have your opinion on those “multi version/demos themes” Is that something you look for , is it a deciding factor when purchasing?
Personally I’m a little puzzled why would someone buy a theme that has multiple demos, since it’s limited for a single usage only (99.5%) of time.
Basically those sellers are selling “bundles” , masqueraded as single theme purchase. Envato should take notice of that.
Interesting read about the subject (found it on hacker news) How the EU VAT rules make EU startups and digital businesses uncompetitive in a global market
Be aware you would need to pay for Extended license if the plan is use the same theme in more than one domain. Having a highly customizable item for a single domain only provides many options and features.
Let’s face it , people don’t buy that kind of themes for single purpose.
Generally when you setup your site once , its done.
Themes that have multiple versions, are only logical for multiple sites / domains.
Since extended licence can’t be enforced , it has no impact on most buyers.
I would really like to know from those authors that offer themes with multiple versions , how many extended licences have they sold?
This could be a brand new topic , so I won’t go in to this further.
ellos said“I would probably choose Royal Theme or X – which are kinda theme clubs within themselves, and that’s it.” Now, that part is scarry.
But – if I have to pay for every theme mandatory support fee then it would be impossible for me to keep up with costs. On top of all that – it would be a hard sell to convince clients to pay yearly support fee for the theme on top of the regular maintenance fee he pays for the site.
At the very least I can say that I will definitely cut down my spending on the theme forest items significantly.
I would probably choose Royal Theme or X – which are kinda theme clubs within themselves, and that’s it.
- Basically when the code is ready, you merge it in to master (development is done on the “development/feature-branch” )
- When the code is merged, you push it to central repository github/bitbucket
-Then you need to setup continuous deployment (google that, and “git web hooks”)
- What happens is that your continuous deployment service detects that the code has been pushed to the master, pulls the code from the repository and replaces to old code.
- If you have unit tests for the code it runs the tests , and deploys only if all tests pass.
And that’s it
Someone mentioned Site Origin Page Builder.
I’ve just checked out that thing, and it is awesome.
And if I understand correctly it is free for commercial use , provided that you don’t bundle it with the theme. You can use TGM to tell the user to download it automatically from the WordPress plugin repository.
And the performance of “multipurpose ultra responsive” themes. Some of those themes are loading megabytes of data. And they are unusable on smartphones and tablets, sure they are “responsive” in the browser, but on mobile device they can’t even be loaded. And “retina ready” themes that are loading 1000px+ width images in to 150×150px thumbs, on regular pixel density systems/ screens.