October 21, 2006
A Flexible Installer for a New Delphi Sales Model
In my "Dreaming a New Delphi Era" I envisioned, among many other elements, "More Alternatives with a Smaller Core IDE, More Subscription Levels , and More Flexible Distribution"... Now there are practical sign this can be the direction DevCo takes with Delphi. Over at non-tech, in this thread, Chris Pattinson (Q&A Manager for BDS, at DevCo) states that (I've edited the text, but the meaning should be preserved):
-
DevCo is working on a new installer technology that would allow them to much more easily provide updates to customers.
-
With this technology, DevCo could stop using the 'old school' model of a major release every year, followed by a big rush of sales.
-
At the opposite, a customer could just buys BDS and then select which modules to update, which components to install, and so on, and pay accordingly for the specific modules or sign up for a subscription with a yearly fee that let's you downlaod each and every module.
- The DevCo development team would need to provide valueable incremental periodic updates to make that attractive. For example, if the team could easily release an update Documentation, or set of Unicode VCL components to subscription users, withoutwaiting for the next major release.
Very interesting model, I think. Also if Borland could turn more and more sales into direct sales, I guess they could benefit of a direct customer relationship and earn a larger amount of what the customers pays, removing one or two (expensive) box-moving operations in between. I still hope that ebooks, training videos, third party components and the like could be involved in the deal. Possibly even a "platinum-subscription-only" newsgroup with access to the Delphi gurus -- who could be paid to dwelll there.
3 Comments
A Flexible Installer for a New Delphi Sales Model
That's the classic good idea that could turn into a nightmare. It could help DevCo. because of a steady cash flow. But it could also mean they deploy new features piece by piece just to justify it - and it could be counterproductive for customers. Or they could not release anything for a given time, and the customer would complain. Although I'd like to buy only what use, let's see how BDS could be partitioned properly. I already use some libraries with complex licensing (i.e. Tom Sawyer), for a beginner is difficult just to understand what she really needs. IMHO I'd prefer a 1.5-2 years release cycle and fixed interval service packs (say each four months), and a paid subscription to obtain them. Service packs should include fixes and some mid-life updates, say .NET 3.0 support if 2.0 is supported, given the former is the latter plus some new libraries.Comment by Kent Morwath on October 23, 16:38
A Flexible Installer for a New Delphi Sales Model
Do you think that they could bribe Marco into living there?Comment by Medbob on October 24, 01:18
Post Your Comment
Click here for posting your feedback to this blog.
There are currently 0 pending (unapproved) messages.



A Flexible Installer for a New Delphi Sales Model
Comment by Zenberg on October 22, 15:53