The Design of Software (CLOSED)

A public forum for discussing the design of software, from the user interface to the code architecture. Now closed.

The "Design of Software" discussion group has been merged with the main Joel on Software discussion group.

The archives will remain online indefinitely.

Basic, Pro & Enterprise - 1 app or 1 app + addins

Just wanting to get your opinion on how shrink wrapped applications are built.

Do they tend to have addins for more advanced functionality or do they keep it all together with switches set on or off depending on the version.

summing up
Tuesday, June 03, 2008

1) More up-front architecture to develop
2) Cleaner separation of additional functionality from standard functionality
3) Defining 1) to achieve 2) can be difficult.
4) May or may not be easier to deploy additional addins without deploying new implementations of the base functionality

Switches set on or off depending on the version: reverse of the above.
Christopher Wells Send private email
Wednesday, June 04, 2008
Most of our current apps have something like what you've described as #2 (diff compiles). I'm working towards add-ins/plugins for a next generation product.

Mostly, the plugin/addin model allows us to upgrade pieces, vs 100-200mb downloads for each new patch (or the incremental updates - like 5.2 to 5.3). The drawback is that if our products were targets of piracy, then anyone who could hack our app could "get it all."

In short, if you have a moderate to serious piracy risk/problem, then you should use different compiles.
If you have a low risk/problem then the plugin model might be a reasonable choice.
Peter Send private email
Wednesday, June 04, 2008

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
Powered by FogBugz