(OT) Embedded db license design/marketing question
(OT) Embedded db license design/marketing question
- Subject: (OT) Embedded db license design/marketing question
- From: "T.G. McLean" <email@hidden>
- Date: Wed, 18 Sep 2002 10:32:51 -0600
Hello, gang --
As I announced in a previous thread, OpenBase (OB) has released a license
for embedding their db.
This brings up a design question someone might have experience / advice
about (one I've already posted to the OB list):
Imagine a customer's purchased my app. with the OB db embedded (I'm
thinking single-user, here). Each year, as a developer, I have to pay for
the license. I pass along the cost in the price new customers have to pay
to get on board. But what about PAST customers, especially those who
think the version of my app. they bought in the past is just fine,
thank-you very much, and they don't need the upgrade? All they will see
is that each January 1st., say, they're locked out of their document, held
hostage to paying for what they'll see as my gravy-train. Pretty soon I'm
no better than Mafiasoft.
As far as I see it, I can (a) eat the cost and make it up in new sales,
ensuring that exisiting customers always keep up to date; or (b) get the
existing customers to cough-up every year. Both of these options have
good and bad sides.
Are there any lessons / advice any users of this list can provide, from
experience or otherwise?
-- TG
------------------
T.G. McLean
Cocoa - C/C++ - SQL - OpenGL - AppleScript - Java - Design
email@hidden
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.