software, business-model, open-sourceI wrote an open source application back in 2011 which I spent all of a month to build with a few enhancements I added over the next month or two. I have since then done some significant enhancements to my application. I own, will own or will rewrite all of the source code, images, etc. If I leave my application with the same name as my open source app, there might be confusion. I really like the name I gave it, so renaming my app is not my first choice. My application is a desktop application which I intend to sell for 10-20 dollars. This is intended for general consumers, not businesses, so a support model doesn’t likely make much sense.
While my enhancements are significant, a fair number of users might be able to get along with the older product. It’s not polished, it lacks some useful features, but it might be acceptable. In looking at the old site I used, I have about 3000 downloads, but no way of contacting those people for marketing purposes.
It is not valuable to suggest that I just keep my application open source. I have tried multiple times to do donations and it doesn’t work for me. I don’t want to try the support model. I’m strongly opposed to building in advertising, so that is not something I am willing to try.
What are the advantages of pull my app from the various sites hosting it? How can I put the cat back into the bag?
What advantages do I get if I just leave my old program around?
Is there is any other pro-open source methods I have failed to consider?
I think you should read these series How to Make Money from Open Source Platforms. You should think about your business model if it is your business (you rely on it as a source of income). If you choose an OpenCore model you can name it something like Elite Foo Bar to distinguish it from the open source Foo Bar, this way you wont loose your current customers and those who need the extra functionality may be willing to pay the bucks. If you are an indie developer with occasional simple apps of course your dynamics might be different but if you plan to grow one application and make it your primary business (or startup company) then you should decide what your exit strategy is. Do you want to provide freemium and gain traction, do you want a million nonpaying users or a handful who pay, both are viable strategies.
But after all, it is your code and you can do whatever you want with it, try to make the most.
Personally I would say your best bet is to remove any trace of your old project and then use the same name for your new project. I would avoid referencing the old project on your website or when marketing the new one as this would only draw attention that you’re moving from free to paid.
Assuming you own the IP for your old project that is but it would be worth speaking to an IP lawyer if you are concerned that someone would have claim to your work.
Leaving your old program around in the public would only harm your new efforts as it would stand as a free version of your paid software. If you were to offer both then it would draw attention that you are now charging for your once free service. That being said, make sure you take a copy of your original work incase you want it for any future works.
You may not be able to put the cat fully back in the bag, as your old project is open source, anyone with a copy of your work CURRENTLY can then reuse/resell it. However if you are confident that your new version is much better then that shouldn’t discourage you as any competition based from your previous work would not be much competition. A quality paid solution is always better than a free partial solution.
I will argue the other side of the coin from the other replies. You should keep your open source heritage.
3000 downloads is not a lot. It’s nothing to scoff at, but ultimately it’s not a lot of trial users.
I’m assuming there is not a single line of code belonging to someone else or another Free Software project. If this is not the case you’ll have to recode your app from scratch (if you haven’t already done so since asking this question in 2015).
Release a bugfix version of the last open source version and rename it to FooBar GPL 1.1 (or whatever version your up to).
FooBar 2.0 (or OpenSource version x+1) is proprietary and for pay. Maybe you’ll offer a trial version or nagware.
How will you feel when your software shows up on a torrent site?
Whatever the feelings you now market FooBar 2.0 as the new direction of the software.
Open source purists are free to fork the old version of the software, but with 3000 downloads it’s unlikely there are developers among them.
You are not obligated to maintain your open source software. You can cease development whenever you choose. But you own the name, even if you haven’t registered a trademark yet.
The initial brand awareness is worth a bit of potentially helpful controversy of moving to closed source.
For the record I don’t think you’ll get enough sales to work on it full time. But I suspect your motivated to work on it now as a closed source app.
I also think selling a great updated desktop version for $47 or more will generate more revenue than your current price point.
All content is licensed under CC BY-SA 3.0.