>No. More complexity means more bugs and less performance or more work
>which means less features or higher price.
No it doesn't mean that for certain.  Bolting on stuff later could mean more 
work and more bugs (depending on the quality of the initial 
design/implementation/code review/test), but designed from the outset its much 
less likely.

And good prefs design doesn't mean complexity for the users understanding 
either - make basic settings easy to find, and select meaningful defaults so 
most users won't need to change them most of the time.  Keep advanced settings 
separated, related settings together.

Options are just another function point to count.

>You can have some options but good software has good defaults and few
>options.
>
There's plenty of good software with many many options, and plenty of bad 
software with few options.  There's no guarantee either way; and no conclusions 
can be made.
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta

Reply via email to