It is a usual practice, and it is inevitable even in the majority of cases, I predict, because customers generally look to get most for their money.
Bang for the Buck
I may say: 'Oh, what a wonderful world of the software applications with the never ending story where more features mean more work to do/upgrade!' :)
Comparing the other worlds e.g. cars or mobile phones we see many similarities.
Who uses more than five features of their phones? ;)
I'm not going to criticize it, or even I may argue that it can be fully acceptable in case the new options are simply manageable, 'turn on/off', e.g. Firefox has add-ons.
Thus, the main question is:
Should the core functionality of the systems be simply manageable as well?
The answer is as always the same: 'It depends ...'
OK, ok, ok. But, why am I bothering about that now? :)
Yesterday I read an interesting post '8 CMS features customers want but never use' and I found this list a little bit surprising. The 8 CMS features (see below) are really common in the RFP (Request for Proposal) which I regularly encounter at my work and I have always been sure that those features are MUST BE not NICE TO HAVE for the CMS customers. I will now have to look at them from the different perspective.
- Color coding changes
- Microsoft Office integration
- Future preview
- Back-end analytics
- Advanced search
- A/B testing
- Frontpage editing
The above mentioned list was created at a meeting of the European CMS Expert Group, which meets regularly to share experiences and sets the agenda for the industry, thus, the list is supported statistically.