Permanent Purchase for Fences?

Is it possible to purchase a permanent license for Fences?

5,056 views 7 replies
Reply #2 Top

Hi kyao2259, We’re seeking feedback on that actually. The permanent purchase link is directly under the subscription purchase button, so we’re not sure how to draw additional attention to this option. Wondering what we might be able to do to make this more visible and apparent.

 

In general we encourage subscription because Windows is updating more than ever, and this helps us ensure users are up to date with the current version.

Reply #3 Top


Is it possible to purchase a permanent license for Fences?
End of quote

At the rate Stardock is pushing out new versions that we are required (or forced, whatever you want to call it) to buy, in my opinion it’s not worth it. Just get a subscription, which seems to be their agenda.

This also goes for Start11. Stay tuned for Start11v3 (no doubt)

Unless you’re planning on bypassing versions.

Reply #4 Top

 

Why don’t you just make the page a 4 quarter and put a Permanent Licence box before the Single Licence box?

 

Reply #5 Top

Simply up the font size a couple of points and change to Bold ...;)

Reply #6 Top

You want people to compare options until the last minute.

Green button takes you to 'clear' purchasing options. "Get permanent license or subscription now!" "Get a license now!"

(permanent license has less resistance, mention first)

Do it on another screen.

Recommend logging in.

Logging in will advertise any savings because of other products on account.

Reply #7 Top

Actually, I know this is a bit of an impertinent suggestions as its such a major pricing model and product change...

But there are a lot of missed opportunities for integration between object desktop family features. (and my guess is duplication of dev work to a degree)
E.g. Fences colourisation and Groupy colourisation.

I think You should:

  • scrap all the separate products.
  • Offer Object desktop as a permanent license product that comes with a permanent license for 1 chosen module high buy in. (eg start 11)
  • Offer further modules that you can upgrade your Object Desktop license with the lesser prices.
  • You can now bring common features like 'colorisation themes' into the Object Desktop framework product.
  • As long as shared features are moved into common frame work, and publish interfaces that must facilitate backwards compatibility.
  • Nothing changes in terms of module licensing and eligibility for updates. You may have one new module and one very out of date module. (It may just be that by chance one old product works for longer than might otherwise, because a shared common component was updated by another module)

version control dependencies will become more complicated, but not impossible. 'Backwards compatibility' is doable and has been achieved successfully in software for as long as I remember.

  • Shared features of the Object Desktop framework, need not be deployed with the framework. They can be deployed by the latest version of the licensed module; which checks to deploy only when it has a later version of the common component. Newer version's interface must, provide backwards compatibility functionality.



Another bonus is that this is another opportunity to upsell to permanent license holders.
Maybe even to spread pricing options for subscription also.

...

Or, it might not be unreasonable to say,
"Sorry, if you want to upgrade a module, you will 'need' to pay to upgrade all the modules you wish to still use"

You will need to pro-rata discount according to which modules were purchased when.
Its like a sub, but its a sub that allows you to download older versions after your sub runs out. (or is that how 'your' sub works now?... I need to check that... I'm assuming that once object desktop sub runs out the software disables....)