Tell me more ×
Answers OnStartups is a question and answer site for entrepreneurs looking to start or run a new business. It's 100% free, no registration required.
up vote 1 down vote favorite

Let say I have a Demo and Full versions of my software. Demo is like a Full but with some missing functionality. Someone installs Demo, try it and decides to purchase Full version. He downloads it and starts installation.

My question is: Do you think it is reasonable full version installer to uninstall Demo version before installing the Full one?

My reasoning is that if there are two versions on the user computer this can confuse him.

share|improve this question

4 Answers

up vote 1 down vote accepted

All of our retail poroducts automatically uninstall the trial version. You don't want to confuse the customer with two products installed at one time, and you don't want to make the new customer do an extra step (uninstall the demo) before the installer will work.

Keep your trial and full versions completely separate. That way there is no way to "crack" the trial version and turn it into a full version.

share|improve this answer
Yes, the reason for this is to keep the trial and full version separate in the way that it is not possible to crack the demo. – Ross Jun 24 '10 at 15:58
up vote 2 down vote

IMHO you should have one install. The full version gets installed in "DEMO" mode, meaning some full-version functionality is disabled or redirected to demo functionality. The switch from demo to full then is an unlocking and/or update exercise. This means the user only ever has one install. I would think this aligns with user expectations.

share|improve this answer
I think it is not good idea to have installed full in "demo" mode, a kind of prevention of unwanted activities. It seem this is what a lot of people suggest. – Ross Jun 24 '10 at 13:59
So full version has extra functions and is branched from your demo version? I normally go limited time period of full version and so its one code source where a key then stops the time period count down. – John Bogrand Jun 24 '10 at 14:34
It is not branched, just a compile switch that disables some things or changes them. For example "save" can be disabled or changed to open the "buy now" web page. "Demo" version is like a marketing tool for the "full" version. – Ross Jun 24 '10 at 15:56
up vote 1 down vote

I would suggest having the code go through an upgrade so it is part of the same base. I would think easier to manage. How much is different from the Demo to the full version?

share|improve this answer
This is good suggestion. – Ross Jun 24 '10 at 16:05
up vote 0 down vote

In my opinion the whole process has to be as transparent as possible to the end users.

Why don't you choose to switch from "demo"/"full" to "full" with an activation code need to unlock the app after the evaluation period has over?

I mean, you have your App and you give 14 days evaluation time. People download it and they found it great. After 14 days, the App stop working asking for the activation code. Enthusiast users will buy the code from your website and they can unlock the code without be bothered in "uninstall/download/install again" tasks.

Does it make sense?

share|improve this answer
There is different type of demo versions. "Time limitied" vestions might be more appropriate for some products, but I choose "time unlimited" with limitation on some of the features that can be used. My personal opinion is that "time limited" model for demo version is broken. Demo version is serving as marketing tool for the full version and I do not want to limit my clients to try as long as they want before deciding to buy. It that not transparant? – Ross Jul 5 '10 at 14:55
Ross, I understand your point. But giving your customer a product that has some features locked is equal to limit their test as you would do limiting in time. It's just a matter of what do you want to limit: "limit the time of the tests but not the features" and "limit the features but they can play with my tool forever". It would be interesting comparing the conversion ratio in the two scenarios. :-) – thesp0nge Jul 5 '10 at 15:04
You are right, the limitation have to be carrefuly choosen. I do not want to limit the product too much and give wrong impression of what it is cappable to do. At the moment i am thinking to limit just "save" feature and probably add somme unobstructive wattermarking more as advertising then protection. – Ross Jul 6 '10 at 9:04

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.